BAPI_PO_CREATE1 - Delivery date regarding

Hi experts.
I am creating PO by function module above. Problem is, that delivery date of order is calculating by system, not by my own proposal.
Is there any method, field in structure or something else to turn off that proposal ... ?
Thanks a lot.

POSCHEDULE structure is filled. Problem is when for example delivery date is in some other date than system wants.
I mean when I want to create PO with long deliv.date like 1 year, system will generate warning (we can see that in ME21). I want omit that warning and create PO with my own deliv.date ...
Thanks.

Similar Messages

BAPI_PO_CREATE1 delivery date ignored by system

Hi, everyone:
I use BAPI: BAPI_PO_CREATE1 to create PO, and I specify the delivery date as following codes. But the system ignored my delivery date and give another one.
"{Schedule line
     CLEAR POSCHEDULE.
     POSCHEDULE-PO_ITEM = EBELP.
     POSCHEDULE-SCHED_LINE = '0001'.
     POSCHEDULE-DEL_DATCAT_EXT = 'D'.
     POSCHEDULE-DELIVERY_DATE = SY-DATUM.
     POSCHEDULE-QUANTITY = IT_ITEM-MENGE.
     POSCHEDULE-STAT_DATE = SY-DATUM.
     POSCHEDULE-PO_DATE = SY-DATUM.
     APPEND POSCHEDULE.
     CLEAR POSCHEDULEX.
     POSCHEDULEX-PO_ITEM = EBELP.
     POSCHEDULEX-SCHED_LINE = '0001'.
     POSCHEDULEX-PO_ITEMX = 'X'.
     POSCHEDULEX-SCHED_LINEX = 'X'.
     POSCHEDULEX-DEL_DATCAT_EXT = 'X'.
     POSCHEDULEX-DELIVERY_DATE = 'X'.
     POSCHEDULEX-QUANTITY = 'X'.
     POSCHEDULEX-STAT_DATE = 'X'.
     POSCHEDULEX-PO_DATE = 'X'.
     APPEND POSCHEDULEX.
What causes this problem?
Thanks in advance.

Hello ,
This works fine for us :
    ls_poschedule-po_item = ls_ekpo-ebelp.
    ls_poschedule-delivery_date = id_delivery_date.
    APPEND ls_poschedule TO lt_poschedule.
    ls_poschedulex-po_item = ls_ekpo-ebelp.
    ls_poschedulex-po_itemx = 'X'.
    ls_poschedulex-delivery_date = 'X'.
    APPEND ls_poschedulex TO lt_poschedulex.
Regards,
Didier

BAPI_PO_CREATE1 - Delivery date

Hi all,
I'm trying to create a PO by BAPI_PO_CREATE1.
The problem is that the PO is created with a default delivery date and no the one I passed it.
I put in the po_schedule table the delivery_Date and also I fill the po_schedulex table, but the new PO has another delivery date. Do Any one know why?
thanks,
enzo

HI Enzo,
This is just for verification...see the fields that you have used in poschedule and poschedulex
Parameter: POSCHEDULE
PO_ITEM              =                    00001
SCHED_LINE           =                    0001
DELIVERY_DATE        =                    02.12.2002
QUANTITY             =                    6.000
Parameter: POSCHEDULEX
PO_ITEM              =                    00001
SCHED_LINE           =                    0001
PO_ITEMX             =                    X
SCHED_LINEX          =                    X
DELIVERY_DATE        =                    X
QUANTITY             =                    X
Pls ignore the reply if you did this already..
Thanks,
Renjith

BAPI_PO_CREATE1 - Delivery date not changing

Hi All,
I ''m using BAPI_PO_CREATE1 for po creation.
When I try to enter the po creation date using the bapi its not taking the value I enter.
It takes from the system .
      it_shed-po_item       = git_input-ebelp.
      it_shed-sched_line    = '0001'.
      it_shed-delivery_date = '25.05.2008'.
      it_shed-stat_date = '25.05.2008'.
      it_shed-quantity      = git_input-menge.
      it_shed-DEL_DATCAT_EXT = 'D'.
      APPEND it_shed.
      it_shedx-po_item   = git_input-ebelp.
      it_shed-sched_line = '0001'.
      it_shedx-po_itemx   = 'X'.
      it_shedx-sched_linex = 'X'.
      it_shedx-delivery_date = 'X'.
      it_shedx-quantity      = git_input-menge.
      it_shedx-DEL_DATCAT_EXT = 'X'.
      it_shedx-stat_date = 'X'.
      APPEND it_shedx.
Please let me know how to enter the date.
Thanks

Hi Ann,
Currently I don´t have a system to test it myself, but can you please try the following:
Replace '25.05.2008' by '20080525', the first is a external format and the second is the format used internally.
I don´t know you copied the code or you have written it again, but the field sched_line in the second structure is still pointing to the first (missing x)..
I hope this helps you!
Good luck!

HOW TO FIND THE REQUIRED DELIVERY DATE IN VA02

hi
HOW TO FIND THE REQUIRED DELIVERY DATE IN VA02.
i want to display this field in my report. what is the fieldname and in which table it is ?

Hi Jyothsna,
There are 2 dates when you say Requested Delivery Date
1. Header level in VBAK-VDATU is the field
2. At item level it is in the schedule line. VBEP-EDATU.
The relationship between item (VBAP ) and schedule line ( VBEP )is 1 to many. But there will be mutiple schedule lines only if you are using the scheduling functionality. Also note to check for confirmed quantity (VBEP-BMENG) to be greater than 0 and use that schedule lines EDATU date as Requested delivery date.
regards,
Advait Gode.

Delivery date and sales order creation date

Dear all
Can you please explain the relation between delivery date and sales order date. In my case i can create delivery with delivery date as before the sales order date... how it is possible that i can create delivery before the sales order date.??
Please explain.........
Warm Regards
Inder Pal

Hi,
Sales order date: Date on which the customer officially places an order to your company.
All the commitment and product allocation counting starts with reference to this date.
e.g. customer says that the goods are required from 20 days of placing order, then from this date the calculation starts.
Delivery date: Date on which after the system goes through material availability date, replenishment time, calculates the date on which physically the goods can be delivered to the customer.
e.g. customer orders 100 qty of material X in 15 days, you will hve to check this delivery date through availability check which can be done in sales order and also delivery.
payment date is based on this delivery date.
regards,
Siddharth.

Shipping notification delivery date 1970

Hi,
For few shipping notifications we see in MD04 the delivery date as 01.01.1970 . How this date is generated for a current shipping notification?
Thanks,
shan

Dear,
If you use Transaction VL02 to apply further items of a sales order to a delivery (deliver the order) and then change header data of the delivery in the same transaction, incorrect updates may occur to statistics which use date fields of the delivery header as the periodicity. due to this affects the update of the cumulative delivered quantity (S073).
If you change header fields of the delivery, the system may not save the changes on the database. The problem occurs, for example, for the delivery date in the shipping notification or in delivery which is not saved with the current status.
In the above case, the old data is cleared with an incorrect date database status of the delivery header has to be in structure YLIKP. Also check the configuration of Sales Document Type " for Requested Delivery Date.-------"Propose Delivery Date"
Regards,
R.Brahmankar

What is the actual delivery date

Hello All,
In the delivery what is the actual delivery date
Regards,
Abhijit Dixit
+91 9820935468

Hi,
The actual delivery date is the date by which your goods reach the customer.
It is field appearing in delivery.
Planned delivery date will be calculated by the system automatically based on the backward or forward delivery scheduling based on which you maintained in your entry there.
But it is the actual date when the goods reach the customer.
Regards,
Krishna.

Problem in BAPI_PO_CREATE1 with delivery date option

Hi Experts,
I'm using BAPI_PO_CREATE1 for uploading user excel file to create purchase orders.
The issue is PO is created successfully but the delivery date is not picking properly. System is picking some other delivery date.
Can any one help me out from this?????????
Any USEFUL INPUTS for solving this issue will be rewarded.
Code :
REPORT zmm_bapi_po_create.
*                             ''~``
*                            ( o o )
*    +------------------.oooO--(_)--Oooo.------------------+
*    | ZMM_BAPI_PO_CREATE -To create Purchase orders       |
*    |                                                     |
*    |                    .oooO                            |
*    |                    (   )   Oooo.                    |
*    +---------------------\ (----(   )--------------------+
*&    Program Name     : ZMM_BAPI_PO_CREATE
*&    Transaction Code :
*&    Module Name      : MM
*&    Developer        : Lakshmiraj.A
*&    Functional       : Xavier
*&    Transport Request:
*&    Program Type     : Report
*&    SAP Release      : 46C
*&****************************REVISION LOG*****************************
*& Log     Date         Author              Description
*&------------------------ TABLE USED --------------------------------*
*&---------------------- VARIABLE DECLARATION ------------------------*
* For Storing file name.
DATA : filename1 TYPE string.
* Flag to identify the matching entries
DATA : flag(1).
* For Display Message
DATA : g_msg(80) TYPE c.
* Declaring that as a character with length 4096.
TYPES truxs_t_text_data(4096) TYPE c OCCURS 0. " Type Group : TRUXS
* Containing RAW Data
DATA : it_raw TYPE truxs_t_text_data.
*&------------------------- INTERNAL TABLE ---------------------------*
DATA: gstest LIKE bapimepoheader.
DATA: g_ebeln LIKE bapimepoheader-po_number.
DATA: BEGIN OF g_bapimepoheader OCCURS 0.
        INCLUDE STRUCTURE bapimepoheader.
DATA: END OF g_bapimepoheader.
DATA: BEGIN OF g_bapimepoheaderx OCCURS 0.
        INCLUDE STRUCTURE bapimepoheaderx.
DATA: END OF g_bapimepoheaderx.
DATA: BEGIN OF g_bapimeposchedule OCCURS 0.
        INCLUDE STRUCTURE bapimeposchedule.
DATA: END OF g_bapimeposchedule.
DATA: BEGIN OF g_poschedulex OCCURS 0.
        INCLUDE STRUCTURE bapimeposchedulx.
DATA: END OF g_poschedulex.
*DATA: BEGIN OF g_bapieikp OCCURS 0.
*        INCLUDE STRUCTURE bapieikp.
*DATA: END OF g_bapieikp.
DATA: BEGIN OF g_bapimepoitem OCCURS 0.
        INCLUDE STRUCTURE bapimepoitem.
DATA: END OF g_bapimepoitem.
DATA: BEGIN OF g_poitemx OCCURS 0.
        INCLUDE STRUCTURE bapimepoitemx.
DATA: END OF g_poitemx.
DATA: BEGIN OF g_bapiret2 OCCURS 0.
        INCLUDE STRUCTURE bapiret2.
DATA: END OF g_bapiret2.
DATA: BEGIN OF itab OCCURS 0,
doc_type       LIKE    bapimepoheader-doc_type,
vendor         LIKE    bapimepoheader-vendor,
purch_org      LIKE    bapimepoheader-purch_org,
pur_group      LIKE    bapimepoheader-pur_group,
comp_code      LIKE    bapimepoheader-comp_code,
incoterms1 LIKE bapimepoheader-incoterms1,
incoterms2 LIKE bapimepoheader-incoterms2,
po_item        LIKE    bapimepoitem-po_item,
material       LIKE    bapimepoitem-material,
short_text     LIKE    bapimepoitem-short_text,
quantity       LIKE    bapimepoitem-quantity,
plant          LIKE    bapimepoitem-plant,
delivery_date LIKE    bapimeposchedule-delivery_date,
END OF itab.
DATA: it_itab LIKE itab OCCURS 0 WITH HEADER LINE.
*&------------------------ SELECTION SCREEN --------------------------*
SELECTION-SCREEN BEGIN OF BLOCK blk WITH FRAME TITLE text-100.
PARAMETERS : p_file LIKE rlgrap-filename.
SELECTION-SCREEN END OF BLOCK blk.
*&-----------------------AT SELECTION SCREEN -------------------------*
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
* For getting input filename
PERFORM get_filename.
*&-----------------------START OF SELECTION---------------------------*
START-OF-SELECTION.
* Open the Excel file and Update with the internal table
PERFORM update_inttable.
PERFORM bapi_upload.
*       FORM bapi_upload                                              *
FORM bapi_upload.
it_itab[] = itab[].
SORT itab BY vendor material.
DELETE ADJACENT DUPLICATES FROM itab COMPARING vendor.
LOOP AT itab.
    g_bapimepoheader-comp_code = itab-comp_code.
    g_bapimepoheader-doc_type = itab-doc_type.
    g_bapimepoheader-creat_date = sy-datum.
    g_bapimepoheader-created_by = sy-uname.
    g_bapimepoheader-vendor = itab-vendor.
    g_bapimepoheader-purch_org = itab-purch_org.
    g_bapimepoheader-pur_group = itab-pur_group.
    g_bapimepoheader-incoterms1 = itab-incoterms1.
    g_bapimepoheader-incoterms2 = itab-incoterms2.
    APPEND g_bapimepoheader.
    g_bapimepoheaderx-comp_code = 'X'.
    g_bapimepoheaderx-vendor = 'X'.
    g_bapimepoheaderx-doc_type = 'X'.
    g_bapimepoheaderx-purch_org = 'X'.
    g_bapimepoheaderx-pur_group = 'X'.
    g_bapimepoheaderx-incoterms1 = 'X'.
    g_bapimepoheaderx-incoterms2 = 'X'.
    APPEND g_bapimepoheaderx.
    LOOP AT it_itab WHERE vendor = itab-vendor.
      MOVE-CORRESPONDING it_itab TO g_bapimepoitem.
      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
           EXPORTING
                input = it_itab-material
           IMPORTING
                output = it_itab-material.
      g_bapimepoitem-material = it_itab-material.
      APPEND g_bapimepoitem.
      g_poitemx-po_item = it_itab-po_item.
      g_poitemx-po_itemx = 'X'.
      g_poitemx-item_cat = 'X'.
      g_poitemx-plant = 'X'.
      g_poitemx-stge_loc = 'X'.
      g_poitemx-net_price = 'X'.
      g_poitemx-acctasscat = 'X'.
      g_poitemx-material = 'X'.
      g_poitemx-short_text = 'X'.
      g_poitemx-matl_group = 'X'.
      g_poitemx-quantity = 'X'.
      g_poitemx-po_unit = 'X'.
      g_poitemx-orderpr_un = 'X'.
      g_poitemx-trackingno = 'X'.
      g_poitemx-delete_ind = 'X'.
      APPEND g_poitemx.
      g_bapimeposchedule-po_item = it_itab-po_item.
      g_bapimeposchedule-sched_line = '001'.
      g_bapimeposchedule-del_datcat_ext = 'X'.
      g_bapimeposchedule-delivery_date = it_itab-delivery_date.
      g_bapimeposchedule-quantity = it_itab-quantity.
      APPEND g_bapimeposchedule.
      g_poschedulex-po_item = it_itab-po_item.
      g_poschedulex-sched_line = '001'.
      g_poschedulex-po_itemx = 'X'.
      g_poschedulex-sched_linex = 'X'.
      g_poschedulex-del_datcat_ext = 'X'.
      g_poschedulex-delivery_date = 'X'.
      g_poschedulex-quantity = 'X'.
      g_poschedulex-deliv_time = 'X'.
      g_poschedulex-stat_date = 'X'.
      APPEND g_poschedulex.
    ENDLOOP.
    CALL FUNCTION 'BAPI_PO_CREATE1'
         EXPORTING
              poheader         = g_bapimepoheader
              poheaderx        = g_bapimepoheaderx
         IMPORTING
              exppurchaseorder = g_ebeln
              expheader        = gstest
         TABLES
              return           = g_bapiret2
              poitem           = g_bapimepoitem
              poitemx          = g_poitemx
              poschedule       = g_bapimeposchedule
              poschedulex      = g_poschedulex.
    IF NOT g_ebeln IS INITIAL.
      COMMIT WORK.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
           EXPORTING
                wait = ''.
      REFRESH : g_bapimepoitem,
                g_bapimepoheader,
                g_bapimepoheaderx,
                g_bapiret2,
                g_poitemx,
                g_bapimeposchedule,
                g_poschedulex.
    ENDIF.
ENDLOOP.
ENDFORM.
*       FORM GET_FILENAME                                             *
FORM get_filename.
CALL FUNCTION 'F4_FILENAME'
       EXPORTING
            program_name = sy-cprog
            dynpro_number = sy-dynnr
            field_name    = ''
       IMPORTING
            file_name     = p_file.
ENDFORM.
*       FORM UPDATE_INTTABLE                                          *
FORM update_inttable.
REFRESH : itab[] , itab.
CLEAR : itab.
IF NOT p_file IS INITIAL.
    CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
     EXPORTING
*     I_FIELD_SEPERATOR         =
       i_line_header            = 'X'
       i_tab_raw_data          = it_raw         " WORK TABLE
       i_filename               = p_file
     TABLES
       i_tab_converted_data     = itab[]    " ACTUAL DATA
     EXCEPTIONS
       conversion_failed        = 1
       OTHERS                   = 2.
    IF sy-subrc NE '0'.
      PERFORM callerr USING 'File Error!'.
      STOP.
    ENDIF.
ELSE.
    PERFORM callerr USING 'Choose the file'.
    STOP.
ENDIF.
ENDFORM.
*       FORM CALLERR                                                  *
* --> TEXT                                                          *
FORM callerr USING text TYPE string.
CALL FUNCTION 'FC_POPUP_ERR_WARN_MESSAGE'
       EXPORTING
            popup_title = 'ZMM_BAPI_PO_CREATE'
            is_error     = 'X'
            message_text = text
            start_column = 30
            start_row    = 8.
ENDFORM.
Regards
~Lakshmiraj~

Hi,
1. In Which system you are trying to run this ???? Are you running in IDES or currently running system?
   The reason may be if you are running in IDES , the factory calender may not be correctly positioned.
2. Also this error will occur at situations like....if your factory calendar will be of 2007 year....but the delievery date which you are giving is of 2008 . So error "delivery date exceeds factory calendar" occurs.
Some useful info for you,
Factory calander is must to run SAP. All the scheduling are calculated based on this only. You can define halidays for factory and assign to the calander. You can have 365 days calander / Sat& SU holiday calander or the holiday can be your wish.
The T code is SCAL. create holidays first. create holiday calendar and assign the holidays in holiday calendar. create factory calender and assign the holiday calendar in factory calendar.The Factory calendar is client specific
Rgds,
Lakshmiraj

Stock Transfer Order: Delivery date issue BAPI_PO_CREATE1

Hi,
I am creating STO using Inbound Delivery data from BAPI_PO_CREATE1
inbound shipping date is 30 may 2014.
Passing below data
HeaderData:
doc_type = 'UB'.     "STO
suppl_plnt     =     '101'
doc_date     =     inbound shipping date.
comp_code     =     '1000'
purch_org = '20'
pur_group     =     '200'
Headerx Data:
doc_type = X
suppl_plnt     =     X
doc_date     =     X.
comp_code     =    X
purch_org = X
pur_group     =   x
Item Data:
Po_item = tabix of loop
Material = material from Inbound delivery item
plant = '101'
strge_loc = W.
Qunatity = from Inbound item only.
ItemX Data:
Po_item = X
Material = X
plant = 'x
strge_loc = X.
Qunatity = X.
Schedule Line Data:
po_item = tabix of loop
schedule_line = '001'
delivery_date = shipping date
del_datcat_ext = 'D'.
Quantity     =     quantity from Inbound item.
call function 'bapi_po_create1'.
     exporting
          poheader = header data
          poheaderx = headerx data
      importing
          exppurchaseorder = po
      table
          return = return
          poitem = item data
          poitemx = itemx data
          poschedule = schedule data
          poschedulex = schedulex data.
when i am creating STO with above method STO is getting created and all data in it also correct but delivery date is 20th june 2014
instead of 30 may 2014.
it is coming as there is planned delivery time that is 21 so it is showing 20th june 2014.
but i need this value as 30th may 2014 only.
please help me on that.
thanks in advance.
Regards,
Gaurav

Hello,
You have to populate internal tables pocond and pocondx with values for itm_number,cond_st_no,cond_count,cond_value,cond_type, currency and change_id. Then call BAPI_PO_CREATE1.
Thanks,
Venu

Delivery date not getting transferred while running BAPI_PO_CREATE1

Hi Experts,
I am passing the delivery date item level delivery schedule to the function module
BAPI_PO_CREATE1. But it's not taking it in.The new PO is gettinig created with blank delivery date. I implemented the OSS notes 858316 & 890901 with no luck in this matter.
Please help.
Regards
Navin

Hi JJ
BADI BBP_DOC_CHANGE_BADI- BUS2201 . while creating PO try to validate them if you are in ecs mode
i believe standard SAP dont recalculate delivery date while creation of PO.
regards
Muthu

Regarding additon of Freight charges and Revised Delivery date in Z Trans

Hi All,
My client is using Z Transaction ZSales_Book(Billing report) and he wants to add two extra fields Freight Charges and Revised Delivery date to this report as it is related to VBAP saled document line item and how can we connect it to VBRP Billing document line item can i know the connecting fileds.
As i passed it to ABAPER as a requirement he asked me the same question..........

Hi
Is it is a revised or request delivery date? Assuming it is a request delivery date i am using request terminology
As you want to add two extra feilds freight charges and Request delivery date.
For Freight Charges - If they are item level freight charges then you give the following tables data - VBAP,KOMV
For Revised Delivery Date - use the following data - VBAP, RV45A-ETDAT also
Regards
Srinath

Regarding the delivery date in sales order

Hai
when we give the inhouse production time in material master and the create a sales order whenever we give the quantity the delivery date does not change according to the quantity
ex :- when i give the inhouse time as 2 days for producing a single material
                but when the quantity in sales 10 no. but delivery date is only 2 days
                     i.e, based sales order quantity delivery date should change
           i need the delivery date as 20 days who to do this give the customizing settings
advance thank's for your reply

Dear,
Please check the timing in work scheduling view. other wise schedule the routing and maintain time there and check your result.
In material Master MRP2 screen you will get Scheduling Screen where you will get
In-house production
GR processing time
Plnd delivery time
These are lot size independent but value in work scheduling view are lot size dependent.
Go to VOV8 and check the Lead time part. If u will maintain lead time of 2 days, the req deliverty date will be 2 days frm order creation date.
You can configure this in the configuration of the Sales document type in VOV8. Here we can specify the value and as per that configuration the date will be defaulted.
Regards,
R.Brahmankar

Regarding delivery dates

hi
if the stock is availabel for a material what will be the delivery date in sales order and if the stock is not available for that material then what will be the delivery date in order
regards
kiran

Hi
The system always tries to confirm the delivery dates for the Requested delivery date entered in the sales order. If it fails to confirm the delivery on that date, then gives a future date.
System considers various lead times while calculating the delivery dates. The lead times are, Transit time, Transportation lead time, Loading time, pick/pack time, Replenishment Lead Time(RLT) etc., These lead times are specified in Route, Shipping point and Material Master.
System initially carriesout backward scheduling to confirm the delivery on requested delivery date and if it fails to confirm, then carriesout forward scheduling.
Thanks,
Ravi

Regarding Delivery date

Hello Gurus
I have a requriement that for a sales order quantity (MTO) say qty is 10 then the delivery date is confirmed as 26.11.2008 based on in house production days in Material Master now if i increase the quantity to say in another sales order or same sales order for qty 600 the delivery is poposed same as 26.11.2008 but i want that to change based on qty say like instead of 26.11.2008 atleast it should say 02.12.2008 or above or some date difference how it is possible
Thanks in advance

Hi rajesh
In MTO , the delivery date will change when the PP and MM part is over . So once the PP confirms that the stock is ready then it will affect the delivery date , as at the time of manufacturing that material ,if the no. of days go up then the same delivery date will trigger in the sales order schedule line .
Say for example , In house production time is 1 day , GR time is 2 days, and you have created the sales order today then the delivery date wont come at all. in MTO .But say if it comes also then check that the delivery date could be 25/11/2008. And production time is more than 3 days then the delivery date will go up, say total no. of days they have taken is 5 days then the delivery date will go to 27/11/2008.
Regards
Srinath

BAPI_PO_CREATE1 - Delivery date regarding

Similar Messages

Maybe you are looking for