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.

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

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.

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

The loading date, transportation date and planned date on the STO are the same as Delivery dates.

Hi,
We have created a Intra plant STO (plant to plant in the same company code). The planned delivery date is 4 days. So if I create a STO today (27th march), the delivery date is 31st march (excl Saturday and Sunday).
During delivery creation, the loading date, transportation date and planned date are also coming as 31st march. The route determination for the given shipping point and route shows 2 days for transit and 4 hours for pick pack. There is no loading time maintained for the given combination.
Can you please advice why are the dates coming the same as delivery date during delivery creation without considering the duration maintained in route determination ?
Thanks!!!
Anuja

Hi,
This is a standard behavior of SAP in case of Stock Transfer PO.
If you want that the delivery date of receiving plant be transferred to supplying plant, please use BADI MD_STOCK_TRANSFER.
Hope this helps.
Regards,
Prashant

PO delivery date and GR date delay list .....???

Hi Experts,
How to get a list GR Delay list of all materials or all Vendors. difference between PO delivery date and GR date different .
my client wants a list of vendor GR delay list .is there any standard T-code or any customizing is required..can you please explain me,
Ex:- PO delivery date is 16-04-2009 , GR date is 25-042009 .
so we ned a lis of which is having GR delay by material or vendor.
Thanks in Advance,
Anthyodaya.

pending.

Sales Invoice date and posting date to be GR date

Hi All
We have intercompany process whre we create PO,delivery with the reference of the PO , then GR with ref to outbound delivery and then invoice w.r.t delivery. Now we want the GR document date to be Posintg date and Billing date while creating invoice document. can any one help in this issue?
Thanks in advance

Hi Retail Guy
Pl create a data transfer routine using T Code VOFM with the help of your ABAPer and assign to the copy control.
You could refer to the data transfer routine FV60C011 for sample code.
Don't forget to update the points.
with kind regards
Sundar

Invoice date and Cancel date

Hi ,
How to get invoice date and cancellation date of a sales order.
My requirement is like this: .... i have to list out all the open orders for a particular date, for example today.
For this i need to display sales orders with any status as well as invoiced and cancelled orders which fall under that particular date.
Hope it's clear.
Regards
Sreenivasa Reddy v.

okay here is a sample code to find the open sales orders for a customer and sales area.
just execute the code and see this is fetch ing the open orders .
<b>now for ur logic enhance the code with date in the select statements so that u will capture the open orders with in the range .</b>
regards,
vijay
REPORT ZEX2 MESSAGE-ID arc NO STANDARD PAGE HEADING.
Tables :kna1,vbak.
SELECT-OPTIONS : so_vkorg FOR vbak-vkorg OBLIGATORY,
                 so_vtweg FOR vbak-vtweg OBLIGATORY,
                 so_spart FOR vbak-spart,
                 so_kunnr FOR kna1-kunnr.
DATA : BEGIN OF sales_open OCCURS 0 ,
       vbeln LIKE vbak-vbeln,
       auart LIKE vbak-auart,
       kunnr LIKE kna1-kunnr,
       bstnk LIKE vbak-bstnk,
       lfstk LIKE vbuk-lfstk,
       fkstk LIKE vbuk-fkstk,
       gbstk LIKE vbuk-gbstk,
       END OF sales_open.
DATA : BEGIN OF itm_sales OCCURS 0,
       vbeln LIKE vbap-vbeln,
       posnr LIKE vbap-posnr,
       matnr LIKE vbap-matnr,
       kwmeng like vbap-kwmeng,
       lfsta LIKE vbup-lfsta,
       lfgsa LIKE vbup-lfgsa,
       fksta LIKE vbup-fksta,
       fksaa LIKE vbup-fksaa,
       gbsta LIKE vbup-gbsta,
       END OF itm_sales.
DATA : l_kunnr LIKE kna1-kunnr,
       l_vkorg LIKE vbak-vkorg,
       l_vtweg LIKE vbak-vtweg,
       l_spart LIKE vbak-spart.
DATA: v_statusl(20) TYPE c,
      v_statusb(20) TYPE c,
      v_statusf(20) TYPE c,
      v_statusg(20) TYPE c,
      v_status(20) TYPE c,
      v_field(1) TYPE c.
data : v_openqty like vbap-kwmeng.
**Selection Screen Validations.
AT SELECTION-SCREEN.
PERFORM validations.
*&      Form Validations
*       text
* --> p1        text
* <-- p2        text
FORM validations.
**Customer
IF NOT so_kunnr[] IS INITIAL.
    SELECT SINGLE kunnr INTO l_kunnr
           FROM kna1
           WHERE kunnr IN so_kunnr.
    IF sy-subrc NE 0.
      MESSAGE e002 WITH text-005.
    ENDIF.
ENDIF.
**Sales Organization
IF NOT so_vkorg[] IS INITIAL.
    SELECT SINGLE vkorg INTO l_vkorg
           FROM tvko
           WHERE vkorg IN so_vkorg.
    IF sy-subrc NE 0.
      MESSAGE e003 WITH text-006.
    ENDIF.
ENDIF.
**Distribution Channel
IF NOT so_vtweg[] IS INITIAL.
    SELECT SINGLE vtweg INTO l_vtweg
            FROM tvkov
            WHERE   vkorg IN so_vkorg
             AND    vtweg IN so_vtweg.
    IF sy-subrc NE 0.
      MESSAGE e004 WITH text-007.
    ENDIF.
ENDIF.
**Division
IF NOT so_spart[] IS INITIAL.
    SELECT SINGLE spart INTO l_spart
            FROM tvta
            WHERE   vkorg IN so_vkorg
            AND     vtweg IN so_vtweg
            AND     spart IN so_spart.
    IF sy-subrc NE 0.
      MESSAGE e005 WITH text-008.
    ENDIF.
ENDIF.
ENDFORM.                    " Validations
Top-of-page.
PERFORM sales_top_of_page.
Start-of-selection.
PERFORM sales_sel.
*&      Form sales_sel
*       text
* --> p1        text
* <-- p2        text
FORM sales_sel.
SELECT vbeln auart kunnr bstnk
     lfstk fkstk gbstk
     INTO TABLE sales_open
     FROM vbakuk
     WHERE vkorg IN so_vkorg
     AND   vtweg IN so_vtweg
     AND   spart IN so_spart
     AND   kunnr IN so_kunnr
     AND gbstk NE 'C'.
LOOP AT sales_open.
    WRITE:/4 sy-vline,
           5 sales_open-vbeln HOTSPOT ON COLOR 2 INTENSIFIED OFF,
           16 sy-vline,
           17 sales_open-auart COLOR 2 INTENSIFIED OFF,
           27 sy-vline,
           28 sales_open-kunnr COLOR 2 INTENSIFIED OFF,
           40 sy-vline,
           41 sales_open-bstnk COLOR 2 INTENSIFIED OFF,
           55 sy-vline,
           56 sales_open-lfstk,
           76 sy-vline,
           77 sales_open-fkstk,
           96 sy-vline,
           97 sales_open-gbstk ,
           117 sy-vline.
    HIDE sales_open-vbeln .
ENDLOOP.
ENDFORM.                    " sales_sel
*&      Form sales_top_of_page
*       text
* --> p1        text
* <-- p2        text
FORM sales_top_of_page.
WRITE:/4 sy-uline(114),
     50 'OPEN SALES ORDERS' COLOR 7 INTENSIFIED ON .
WRITE: /4 sy-vline,
          5 'SalesOrder' COLOR 1 ,
          16 sy-vline,
         17 'OrderType' COLOR 1,
         27 sy-vline,
         28 'Customer' COLOR 1,
         40 sy-vline,
         41 'PoNumber' COLOR 1,
         55 sy-vline,
         56 'Delivery Status' COLOR 1,
         76 sy-vline,
         77 'Billing Status' COLOR 1,
         96 sy-vline,
         97 'Processing Status' COLOR 1,
         117 sy-vline .
WRITE:/4 sy-uline(114).
ENDFORM.                    " sales_top_of_page
AT LINE-SELECTION.
SELECT       a~vbeln
               a~posnr
               a~matnr
               a~kwmeng
               b~lfsta
               b~lfgsa
               b~fksta
               b~fksaa
               b~gbsta
               INTO TABLE itm_sales
               FROM vbap AS a JOIN vbup AS b
               ON a~vbeln EQ b~vbeln
               AND a~posnr EQ b~posnr
               AND b~gbsta NE 'C'
               WHERE a~vbeln EQ sales_open-vbeln.
IF NOT sales_open IS INITIAL.
    LOOP AT itm_sales.
      at end of vbeln .
      sum.
      v_openqty = itm_sales-kwmeng.
      endat.
      WRITE:/5 itm_sales-vbeln,
                itm_sales-posnr,
                itm_sales-matnr,
                itm_sales-kwmeng,
                itm_sales-lfsta,
                itm_sales-lfgsa,
                itm_sales-fksta,
                itm_sales-fksaa,
                itm_sales-gbsta.
    ENDLOOP.
ENDIF.
skip 2.
write:/ 'open
Quantity for the order is ', v_openqty .

Difference between Invoice created date and billing date.

Hi Gurus,
I opened the Billing Document in display mode(T.Code:VF03).In header data I found two tabs one is Created On and another one is Billing Date. Here in the billing document the both dates were different.
Please let me know the difference between Created On date and Billing Date.
your afforts are highly appriciated.
JYothi.

Dear Jyothisd,
Invoice created date : Invoice created date is nothing but the date on which you have created the invoice.
Billingdate:Billing date is the date on which you suppose to do the billing for respective customer. Tease billing dates will be proposed to invoice from sales order if it is order related or else actual goods issue date is proposed to billing document as a Billing date if particular billing document is delivery related.
If you want you can change the Actual billing date the result is invoice created date.
Please revert if you want any further clarifications
Thanks&Regards

The Difference between "Cell Data" and "Dimension Data"?

What is the difference between the tab "Cell Data" and "Dimension Data" in SSAS?

Article quote: " SSAS provides the way to secure analysis services database/cube data from unauthorized access. Analysis services provides secure access by creating object called "roles". After creation of role, user's windows login credential can be used
to enroll into particular role because analysis services identifies user from their windows login credentials . You can protect your data in roles at two levels:
1) Dimension level
2) Cell level
If user has been assigned more than one role, analysis services loop through all assigned roles after login. Analysis services finds all permission level for the particular user and union all the permission levels.
If two roles has contradictory access for user then particular access will be allowed. Suppose role1 says Australia data access and role2 denies Australia data access then access to Australia data will be allowed. "
LINK:
http://www.msbiconcepts.com/2010/10/ssas-data-security-dimension-and-cell.html
Kalman Toth Database & OLAP Architect
IPAD SELECT Query Video Tutorial 3.5 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

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 companys 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.

Query on fetching the no.of days between Invoice date and due date in rtf template embedded BI Publisher Report

Hi Experts,
We have a requirement to fetch the value of 'No of days' between Invoice date and due date (Two variable date fields on the template) in an Analysis.
Please let me know the procedure of how to achieve the same.
Regards,
Rev

it's good for ideas but implementation a bit different
Oracle Business Intelligence Publisher Report Designer's Guide
This function provides a method to get the difference between two dates in the given locale. The dates need to be in "yyyy-MM-dd" format. This function supports only the Gregorian calendar. The syntax is as follows:
<?xdoxslt:date_diff(‘format’, ‘YYYY-MM-DD’, ‘YYYY-MM-DD’, $_XDOLOCALE, $_XDOTIMEZONE)?>
where
format is the time value for which the difference is to be calculated
Example:
<?xdoxslt:date_diff(‘d’, ‘2006-04-08’, ‘2006-04-01’, $_XDOLOCALE, ‘America/Los_Angeles’)?>
returns
-7

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

Downloding the SAP master data and transaction data to a flat file

Hello All,
Is there any SAP standard method or transaction to download the SAP master data and transaction data to flat file.
With out using ABAP development, SAP had provided any tool or method to download the SAP system master and transaction data to flat file.
Thanks,
Feroz.

hi
as of now up to my knowledge no.

Doubts in statistic Delivery Date and Commited Date in STO PO

Similar Messages

Maybe you are looking for