ISupplier Forecasting, sales order demand and current INV levels?

Hello,
My organization is considering implementing Oracle iSupplier. In playing with this in a test environment, I see that sales order demand and inventory levels are not pulled into the forecast. All I have been able to do is a blanket release against the blanket agreement and the qty that I put on the release is passed to the supplier side of the application. Is that it? I was hoping to have a more sophisticated calc on demand. Do I not have this setup correctly in me test environment?
Thanks
KPP

>
Our need is to include the demand from sales order and current INV levels. Is that "do-able" with standard PO's? >
There is no way to translate demand from Sales orders into PO automatically. You have a couple of options
1) Use ATO / back-to-back order functionality. That will create a Requisition / PO whenever a order is booked. And the PO will be visible in iSupplier. However, this will NOT look at onhand.
2) Run min-max planning. This will automatically create requisitions / PO when your onhand falls below required minimum. You can configure this to optionally look at open sales orders. Once the PO is approved, it will show up on iSupplier.
Hope this helps,
Sandeep Gandhi

Similar Messages

Urgent!!!Need code to fetch all sales order data and download to flat file

urgent!!!Need code to fetch all sales order data and download to flat file

              D A T A B A S E T A B L E S                          *
TABLES: vbak,                          "Sales Document: Header Data
        VBAP,                          "Sales Document: Item Data
        MARA,VAPMA,VBPA,VBLB,VBEP,
         VBKD.   "Murali Poli                         .
              I N T E R N A L   T A B L E S                         *
Internal table to hold the Delphi material numbers file
DATA: BEGIN OF tbl_matnr OCCURS 0,
        matnr LIKE mara-matnr,         "Material number
      END   OF tbl_matnr.
Internal table to hold customer cross ref data
DATA: BEGIN OF TBL_CUST_SA OCCURS 0,
        OLD_KUNNR LIKE KNA1-KUNNR,     "Old Customer
        OLD_VKORG LIKE A004-VKORG,     "Old Sales organisation
        OLD_VTWEG LIKE A004-VTWEG,     "Old Distribution channel
        NEW_KUNNR LIKE KNA1-KUNNR,     "New Customer
        NEW_VKORG LIKE A004-VKORG,     "New Sales organisation
        NEW_VTWEG LIKE A004-VTWEG,     "New Distribution channel
        PARVW LIKE VBPA-PARVW ,         "Partner function
END   OF TBL_CUST_SA.
Internal table to check the material numbers of the input file
DATA: tbl_mara LIKE tbl_matnr OCCURS 0 WITH HEADER LINE.
Work area to hold the header record
DATA: BEGIN OF w_sa_header,
         recordtype(1),                "Record type
         schedulingagreement(4),       "SA Type
         contractreference(10),        "Contract Reference
         salesorg(4),                  "Sales Organization
         distrchannel(2),              "Distribution channel
         division(2),                  "Sales division
         PONUMBER(35),                 "Purchase order number"gsbhondave
         soldtoparty(12),              "Sold-to party
         shiptoparty(12),              "Ship-to party
         collectivenumber(10),         "Collective number
         description(40),              "Description
         roundqty(13),                 "Rounding Qty
         pdsi(4),                                           "PDI
         correctiondeliverydate(8),    "Correction Delivery Dt
         correctionqty(13),            "Correction Qty
         cumulativereceivedqty(13),    "Cumulative Received Qty
         forecastdeliveryschedule(17), "Forecast Delivery Schedule
         forecastdelscheddate(8),      "Forecast Delivery Schedule Dt
         jitdeliveryschedule(17),      "JIT Delivery Schedule
         jitdeliveryscheduledate(8),   "JIT Delivery Schedule Dt
         materialnumber(18),           "Material number
         plant(4),                     "Plant
         item_category(4),             "Item Category
         suppliercode(15),             "Supplier code
         scac(4),                      "SCAC
         deloc(12),                    "DELOC
         pkg_id(12),                   "Packaging ID
         catno(30),                    "Ultimate Cust Part
         lgort(4),                     "Storage Location
         vstel(4),                     "Shipping point
Adding fields by Murali Poli
         VSBED(2),                     "Shipping conditions
         INCO1(3),                     "Incoterms (part 1)
         INCO2(28),                    "Incoterms (part 2)
         ZECN(1),                      "Engineering Change Letter
End of Adding fields by Murali Poli
       END OF w_sa_header.
Work area to hold the forecast record
DATA: BEGIN OF w_sa_forecast,
         recordtype(1),                "Record Type
         dateformat(1),                "Date format
         forecastdate(8),              "Forecast date
         forecastorderqty(13),         "Order Qty
       END OF w_sa_forecast.
Work area to hold the jit record
DATA: BEGIN OF w_sa_jit,
         recordtype(1),                "Record Type
         dateformat(1),                "Date format
         jitdate(8),                   "JIT date
         jittime(6),                   "JIT Time
         jitorderqty(13),              "Order Qty
       END OF w_sa_jit.
Internal table to hold the Extracted data
DATA: BEGIN OF tbl_record OCCURS 0,
        record_type,
        DATA(400), " changed from 325 to 400
       END OF tbl_record.
Internal table to capture the errors
DATA: BEGIN OF tbl_error OCCURS 0,
        error_text(135),
      END   OF tbl_error.
Internal table to hold the records of VBAP_VAPMA
DATA: BEGIN OF tbl_vbap_vapma OCCURS 0,
VBELN LIKE VAPMA-VBELN, "Sales and distribution document number
POSNR LIKE VAPMA-POSNR,                "Item number
AUART LIKE VAPMA-AUART,                "SA Type
VKORG LIKE VAPMA-VKORG,                "Sales Organization
VTWEG LIKE VAPMA-VTWEG,                "Distribution channel
SPART LIKE VAPMA-SPART,                "Division
KUNNR LIKE VAPMA-KUNNR,                "Sold-to
       plavo like vbap-plavo, "PDI
MATNR LIKE VAPMA-MATNR,                "Material number
WERKS LIKE VAPMA-WERKS,                "Plant
TRVOG LIKE VAPMA-TRVOG,                "Transaction group
VBTYP LIKE VBAK-VBTYP, "SD document category "Murali Poli
VSBED LIKE VBAK-VSBED, "Shipping conditions   "Murali Poli
BSTNK LIKE VBAK-BSTNK, " Purchase order number " gsbhondave
KTEXT LIKE VBAK-KTEXT,
VGBEL LIKE VBAP-VGBEL,                 "Reference document no
ABLFZ LIKE VBAP-ABLFZ,                 "Rounding qty
PSTYV LIKE VBAP-PSTYV,                 "Item category
LGORT LIKE VBAP-LGORT,                 "Storage location
VSTEL LIKE VBAP-VSTEL,                 "Shipping point
END   OF TBL_VBAP_VAPMA.
DATA: BEGIN OF TBL_VBAP OCCURS 0,
VBELN LIKE VAPMA-VBELN,
POSNR LIKE VAPMA-POSNR,
VGBEL LIKE VBAP-VGBEL,
ABLFZ LIKE VBAP-ABLFZ,
PSTYV LIKE VBAP-PSTYV,
LGORT LIKE VBAP-LGORT,
VSTEL LIKE VBAP-VSTEL,
END   OF TBL_VBAP.
Adding by Murali Poli
DATA:BEGIN OF TBL_VBKD OCCURS 0,
      VBELN LIKE VBKD-VBELN,
      POSNR LIKE VBKD-POSNR,
      INCO1 LIKE VBKD-INCO1,
      INCO2 LIKE VBKD-INCO2,
     END OF TBL_VBKD.
End by Murali Poli
Internal table to hold temporarily the records of VBAP_VAPMA
DATA: tbl_vbap_vapma_temp LIKE tbl_vbap_vapma OCCURS 0 WITH HEADER LINE.
Internal table to hold the records of VBPA
DATA: BEGIN OF tbl_vbpa OCCURS 0,
        vbeln LIKE vbpa-vbeln,         "Sales and distribution
                                       "document number
        posnr LIKE vbpa-posnr,         "Item number
        parvw LIKE vbpa-parvw,         "SP Partner type
        kunnr LIKE vbpa-kunnr,         "Customer number
        lifnr LIKE vbpa-lifnr,         "SCAC code     "DN3K923909
      END   OF tbl_vbpa.
Internal table to hold the records of VBLB (Forecast)
DATA: BEGIN OF tbl_vblb_forecast OCCURS 0,
        vbeln LIKE vblb-vbeln,
        posnr LIKE vblb-posnr,
        abart LIKE vblb-abart,        "Release type
        abefz LIKE vblb-abefz,        "Cumulative Quantity
                                       "Received by Customer
        labnk LIKE vblb-labnk,        "Delivery schedule
        abrdt LIKE vblb-abrdt,        "Deivery date
        gjkun LIKE vblb-gjkun,         "Current fiscal year
        vjkun LIKE vblb-vjkun,         "Previous fiscal year
      END   OF tbl_vblb_forecast.
Internal table to hold the records of VBLB (JIT)
DATA: BEGIN OF tbl_vblb_jit OCCURS 0,
        vbeln LIKE vblb-vbeln,
        posnr LIKE vblb-posnr,
        abart LIKE vblb-abart,        "Release type
        abefz LIKE vblb-abefz,        "Cumulative Quantity
                                       "Received by Customer
        labnk LIKE vblb-labnk,        "Delivery schedule
        abrdt LIKE vblb-abrdt,        "Deivery date
        gjkun LIKE vblb-gjkun,         "Current fiscal year
        vjkun LIKE vblb-vjkun,         "Previous fiscal year
      END   OF tbl_vblb_jit.
Internal table to hold the Forecast Schedule lines
DATA: BEGIN OF tbl_vbep_forecast OCCURS 0,
       vbeln LIKE vbep-vbeln,          "Sales document
       posnr LIKE vbep-posnr,          "Item number
       etenr LIKE vbep-etenr,          "Schedule line
       edatu LIKE vbep-edatu,          "Schedule line date
       ezeit LIKE vbep-ezeit,          "Arrival time       "DN3K923909
       wmeng LIKE vbep-wmeng,          "Order quantity in sales units
       prgrs LIKE vbep-prgrs, "Date type (day, week, month, interval)
       abart LIKE vbep-abart,          "Release type       "DN3K923909
      END   OF tbl_vbep_forecast.
Internal table to hold the JIT Schedule lines
DATA: BEGIN OF tbl_vbep_jit OCCURS 0,
       vbeln LIKE vbep-vbeln,          "Sales document
       posnr LIKE vbep-posnr,          "Item number
       etenr LIKE vbep-etenr,          "Schedule line
       edatu LIKE vbep-edatu,          "Schedule line date
       ezeit LIKE vbep-ezeit,          "Arrival time
       wmeng LIKE vbep-wmeng,          "Order quantity in sales units
       prgrs LIKE vbep-prgrs, "Date type (day, week, month, interval)
       abart LIKE vbep-abart,          "Release type      "DN3K923909
      END   OF tbl_vbep_jit.
Internal table for Long texts
DATA: tbl_tline LIKE tline OCCURS 0 WITH HEADER LINE.
                V A R I A B L E S                                   *
DATA: v_count               TYPE i,
      V_REPID               LIKE SY-REPID,
      w_eins                LIKE vbap-umvkz VALUE 1,
      v_cumulative_deli_qty LIKE vblb-abefz,
      v_text_name           LIKE thead-tdname,
      v_week                LIKE scal-week,
      v_count_h             TYPE i,    "Count of header records
      v_count_f             TYPE i,    "Count of Forecast records
      v_count_j             TYPE i,    "Count of JIT records
      v_count_t             TYPE i.    "Count of Shipping instructions
TYPES: unixfile LIKE rlgrap-filename,
       unixdir LIKE rlgrap-filename.
DATA: v_file1 TYPE unixfile,
      v_file2 TYPE unixfile.
DATA: tbl_dynpfields LIKE dynpread OCCURS 0 WITH HEADER LINE.
*data tbl_cust_sa.
      S E L E C T - O P T I O N S / P A R A M E T E R S             *
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
         Valid-to date
PARAMETER:
          p_gueen like vbak-gueen obligatory,
         Correction Delivery date
           P_DELDT LIKE VBAK-GUEEN OBLIGATORY.
Begin of Changes - TIR-40266
              Plant
SELECT-OPTIONS: s_werks FOR vbap-werks.
*SD document category
SELECT-OPTIONS: S_VBTYP FOR VBAK-VBTYP OBLIGATORY." Murali Poli
         Sales organization
SELECT-OPTIONS: S_VKORG FOR VBAK-VKORG OBLIGATORY.
End   of Changes - TIR-40266
SELECTION-SCREEN SKIP 1.
PARAMETER:      r1 RADIOBUTTON GROUP rg1.
         Material numbers file
PARAMETER: P_FILE1 LIKE RLGRAP-FILENAME.
PARAMETER: P_FILE6 LIKE RLGRAP-FILENAME.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(32) text-003.
SELECTION-SCREEN POSITION 33.
         SD SA Extract file
PARAMETER: P_FILE2 LIKE RLGRAP-FILENAME
DEFAULT 'C:\sd_sa_extract.txt'.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN SKIP 2.
PARAMETER:      r2 RADIOBUTTON GROUP rg1.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(32) text-004.
SELECTION-SCREEN POSITION 33.
PARAMETER: p_path1 TYPE unixdir OBLIGATORY DEFAULT '/tmp/'.
SELECTION-SCREEN END OF LINE.
         Material numbers file
PARAMETER: PU_FILE1 LIKE RLGRAP-FILENAME.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(32) text-003.
SELECTION-SCREEN POSITION 33.
         SD SA Extract file
PARAMETER: PU_FILE2 LIKE RLGRAP-FILENAME.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(64) text-005.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END   OF BLOCK b1.
        A T S E L E C T I O N   S C R E E N   E V E N T S          *
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file1.
v_repid = syst-repid.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
       EXPORTING
            program_name = v_repid
       CHANGING
            file_name     = p_file1
       EXCEPTIONS
            mask_too_long = 1
            OTHERS        = 2.
IF sy-subrc <> 0.
    MESSAGE e009.
Message shown as 'Error while getting the file name'
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE6.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
       EXPORTING
            program_name = v_repid
       CHANGING
            FILE_NAME     = P_FILE6
       EXCEPTIONS
            mask_too_long = 1
            OTHERS        = 2.
IF sy-subrc <> 0.
    MESSAGE e009.
Message shown as 'Error while getting the file name'
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file2.
v_repid = syst-repid.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
       EXPORTING
            program_name = v_repid
       CHANGING
            file_name     = p_file2
       EXCEPTIONS
            mask_too_long = 1
            OTHERS        = 2.
IF sy-subrc <> 0.
    MESSAGE e009.
Message shown as 'Error while getting the file name'
ENDIF.
AT SELECTION-SCREEN ON RADIOBUTTON GROUP rg1.
IF r1 = 'X'.
    IF p_file1 = '' OR p_file2 = ''.
      MESSAGE w000 WITH 'Please select a PC file'.
    ENDIF.
    LOOP AT SCREEN.
      IF screen-name = 'P_FILE1' OR
         screen-name = 'P_FILE2'.
        screen-input = '1'.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
ELSEIF r2 = 'X'.
    PERFORM get_value USING 'P_PATH1' CHANGING p_path1.
    PERFORM get_value USING 'PU_FILE1' CHANGING pu_file1.
    PERFORM get_value USING 'P_PATH1' CHANGING p_path1.
    PERFORM get_value USING 'PU_FILE2' CHANGING pu_file2.
    IF pu_file1 = '' OR pu_file2 = ''.
      MESSAGE w000 WITH 'Please select a UNIX file'.
      LOOP AT SCREEN.
        IF screen-name = 'PU_FILE1' OR
           screen-name = 'PU_FILE2'.
          screen-input = '1'.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ENDIF.
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR pu_file1.
PERFORM get_value USING 'P_PATH1' CHANGING p_path1.
PERFORM get_value USING 'PU_FILE1' CHANGING pu_file1.
PERFORM popup_unix_filename CHANGING p_path1 pu_file1.
PERFORM set_value USING 'P_PATH1' p_path1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR pu_file2.
PERFORM get_value USING 'P_PATH1' CHANGING p_path1.
PERFORM get_value USING 'PU_FILE2' CHANGING pu_file2.
PERFORM popup_unix_filename CHANGING p_path1 pu_file2.
PERFORM set_value USING 'P_PATH1' p_path1.
                 T O P - O F - P A G E                              *
TOP-OF-PAGE.
PERFORM delphi_header(z_delphi_header_footer)
     USING
     'E & S SD SCHEDULING AGREEMENTS EXTRACT DATA'(016)
      space
      sy-linsz.
           S T A R T - O F - S E L E C T I O N                     *
START-OF-SELECTION.
IF r1 = 'X'.
    PERFORM upload_data_from_pc_files.
ELSEIF r2 = 'X'.
    PERFORM upload_data_from_unix_files.
ENDIF.
PERFORM check_input_data.
PERFORM get_sd_sa_data.
               E N D - O F - S E L E C T I O N                      *
END-OF-SELECTION.
PERFORM process_data.
                    S U B - R O U T I N E S                          *
*&      Form get_value
FORM get_value USING value(p_fieldname)
            CHANGING value(p_fieldvalue).
IF v_repid IS INITIAL.
    v_repid = syst-repid.
ENDIF.
REFRESH: tbl_dynpfields.
CLEAR: tbl_dynpfields.
tbl_dynpfields-fieldname = p_fieldname.
APPEND tbl_dynpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
       EXPORTING
            dyname               = v_repid
            dynumb               = '1000'
       TABLES
            dynpfields           = tbl_dynpfields
       EXCEPTIONS
            invalid_abapworkarea = 1
            invalid_dynprofield = 2
            invalid_dynproname   = 3
            invalid_dynpronummer = 4
            invalid_request      = 5
            no_fielddescription = 6
            invalid_parameter    = 7
            undefind_error       = 8
            double_conversion    = 9
            stepl_not_found      = 10
            OTHERS               = 11.
IF syst-subrc = 0.
    READ TABLE tbl_dynpfields INDEX 1.
    p_fieldvalue = tbl_dynpfields-fieldvalue.
ENDIF.
REFRESH: tbl_dynpfields.
ENDFORM.                               " get_value
      FORM POPUP_UNIX_FILENAME                                      *
Pops up dialog box to explore the unix filesystem and select a file *
--> VALUE(P_PATH)      Path where to start exploring from         *
--> VALUE(P_FILENAME) Default filename in the dialog box         *
FORM popup_unix_filename CHANGING value(p_path) TYPE unixdir
                                  value(p_filename) TYPE unixfile.
DATA: v_length TYPE i,
       v_filename TYPE unixfile,
       v_directory LIKE draw-filep,
       v_file LIKE draw-filep.
IF p_filename(1) = '/' OR
    p_path IS INITIAL.
   v_filename = p_filename.
ELSE.
   v_length = strlen( p_path ) - 1.
   IF p_path+v_length(1) <> '/'.
     CONCATENATE p_path '/' INTO p_path.
   ENDIF.
   CONCATENATE p_path p_filename INTO v_filename.
ENDIF.
CALL FUNCTION 'Z_UNIX_FILENAME_GET'
      EXPORTING
           def_filename     = v_filename
           mask             = ',*.'
           mode             = 'G'
           title            = 'Get UNIX file...'
      IMPORTING
           filename         = v_filename
      EXCEPTIONS
           inv_winsys       = 1
           no_batch         = 2
           selection_cancel = 3
           selection_error = 4
           OTHERS           = 5.
CHECK syst-subrc = 0.
CALL FUNCTION 'CV120_SPLIT_PATH'
      EXPORTING
           pf_path = v_filename
      IMPORTING
           pfx_path = v_directory
           pfx_file = v_file
      EXCEPTIONS
           OTHERS   = 1.
CHECK syst-subrc = 0.
IF v_directory = p_path.
   p_filename = v_file.
ELSE.
   p_filename = v_filename.
ENDIF.
ENDFORM.
      FORM SET_VALUE                                                *
Sets the value of a field on the selection screen.                  *
--> VALUE(P_FIELDNAME)   Name of the field on the selection screen*
--> VALUE(P_FIELDVALUE) Value of the field                       *
FORM set_value USING value(p_fieldname)
                     value(p_fieldvalue).
IF v_repid IS INITIAL.
    v_repid = syst-repid.
ENDIF.
CLEAR: tbl_dynpfields.
tbl_dynpfields-fieldname = p_fieldname.
tbl_dynpfields-fieldvalue = p_fieldvalue.
APPEND tbl_dynpfields.
CALL FUNCTION 'DYNP_VALUES_UPDATE'
       EXPORTING
            dyname               = v_repid
            dynumb               = '1000'
       TABLES
            dynpfields           = tbl_dynpfields
       EXCEPTIONS
            invalid_abapworkarea = 1
            invalid_dynprofield = 2
            invalid_dynproname   = 3
            invalid_dynpronummer = 4
            invalid_request      = 5
            no_fielddescription = 6
            undefind_error       = 7
            OTHERS               = 8.
ENDFORM.
*&      Form upload_data_from_pc_files
This subroutine is used to upload the data from input files
FORM upload_data_from_pc_files.
REFRESH: tbl_matnr.
CLEAR:   tbl_matnr.
Upload the data from Delphi Materials file
CALL FUNCTION 'WS_UPLOAD'
       EXPORTING
            filename                = p_file1
            filetype                = 'DAT'
       TABLES
            data_tab                = tbl_matnr
       EXCEPTIONS
            conversion_error        = 1
            file_open_error         = 2
            file_read_error         = 3
            invalid_type            = 4
            no_batch                = 5
            unknown_error           = 6
            invalid_table_width     = 7
            gui_refuse_filetransfer = 8
            customer_error          = 9
            OTHERS                  = 10.
IF sy-subrc <> 0.
    MESSAGE e008 WITH 'Materials file'.
Message shown as "Error while reading Materials file"
ENDIF.
IF sy-subrc = 0 AND tbl_matnr[] IS INITIAL.
    MESSAGE e013 WITH 'Materials'.
Message shown as "No records found in Materials file"
ENDIF.
DELETE tbl_matnr WHERE matnr = ''.
CALL FUNCTION 'WS_UPLOAD'
       EXPORTING
            FILENAME                = P_FILE6
            filetype                = 'DAT'
       TABLES
            DATA_TAB                = TBL_CUST_SA
       EXCEPTIONS
            conversion_error        = 1
            file_open_error         = 2
            file_read_error         = 3
            invalid_type            = 4
            no_batch                = 5
            unknown_error           = 6
            invalid_table_width     = 7
            gui_refuse_filetransfer = 8
            customer_error          = 9
            OTHERS                  = 10.
IF sy-subrc <> 0.
    MESSAGE E008 WITH 'Customer/Sales Area Cross Reference file'.
Message shown as "Error while reading Materials file"
ENDIF.
ENDFORM.                               " upload_data_from_pc_files
*&      Form upload_data_from_unix_files
This subroutine is used to upload the data from UNIX files
FORM upload_data_from_unix_files.
REFRESH: tbl_matnr.
CLEAR:   tbl_matnr.
Get the complete filename for the Materials file
PERFORM get_full_filename USING pu_file1 CHANGING v_file1.
Open the Materials file
PERFORM open_dataset USING v_file1 'I' 'T' 1.
CHECK syst-subrc = 0.
Read the materials file
DO.
    READ DATASET v_file1 INTO tbl_matnr.
    IF syst-subrc <> 0.
      EXIT.
    ENDIF.
Populate the read data into the internal table
    APPEND tbl_matnr.
ENDDO.
PERFORM close_dataset USING v_file1.
ENDFORM.                               " upload_data_from_unix_files
      FORM GET_FULL_FILENAME                                        *
Uses the logical path if necessary to get the full filename         *
If the filename already has a directory specified, that itself will *
be the full filename                                              *
Else the logical path for Conversions will be prefixed to the given *
filename                                                          *
FORM get_full_filename USING value(p_file) TYPE unixfile
                    CHANGING value(p_fullfile) TYPE unixfile.
DATA: v_length TYPE i.
IF p_file(1) = '/' OR
    p_path1 IS INITIAL.
   p_fullfile = p_file.
ELSE.
   v_length = strlen( p_path1 ) - 1.
   IF p_path1+v_length(1) = '/'.
     CONCATENATE p_path1 p_file INTO p_fullfile.
   ELSE.
     CONCATENATE p_path1 '/' p_file INTO p_fullfile.
   ENDIF.
ENDIF.
ENDFORM.
      FORM OPEN_DATASET                                             *
Opens dataset in the specified mode                                 *
--> VALUE(P_FILE)    Name of file to be opened                    *
--> VALUE(P_IOMODE) 'I' for Input / 'O' for Output               *
--> VALUE(P_BTMODE) 'T' for Text / 'B' for Binary                *
--> VALUE(P_LEVEL)   If set to > 1, will write error message to   *
                       list Else will supress the error message but *
                       will be available in SYST-MSGV1              *
FORM open_dataset USING value(p_file) TYPE unixfile
                        value(p_iomode) TYPE c
                        value(p_btmode) TYPE c
                        value(p_level) TYPE i.
DATA: v_rc LIKE syst-subrc,
        v_msg(100),
        v_listmsg(100).
IF p_iomode = 'O'.
    IF p_btmode = 'B'.
      OPEN DATASET p_file FOR OUTPUT IN BINARY MODE MESSAGE v_msg.
    ELSE.
      OPEN DATASET p_file FOR OUTPUT IN TEXT MODE MESSAGE v_msg.
    ENDIF.
ELSE.
    IF p_btmode = 'B'.
      OPEN DATASET p_file FOR INPUT IN BINARY MODE MESSAGE v_msg.
    ELSE.
      OPEN DATASET p_file FOR INPUT IN TEXT MODE MESSAGE v_msg.
    ENDIF.
ENDIF.
IF syst-subrc <> 0.
    v_rc = syst-subrc.
    syst-msgv1 = v_msg.
    IF p_level > 0.
      CONCATENATE 'Unable to open' p_file
             INTO v_listmsg
        SEPARATED BY space.
      IF p_iomode = 'O'.
        CONCATENATE v_listmsg 'for Output'
               INTO v_listmsg
          SEPARATED BY space.
      ELSE.
        CONCATENATE v_listmsg 'for Input'
               INTO v_listmsg
          SEPARATED BY space.
      ENDIF.
      IF p_iomode = 'B'.
        CONCATENATE v_listmsg 'in Binary mode'
               INTO v_listmsg
          SEPARATED BY space.
      ELSE.
        CONCATENATE v_listmsg 'in Text mode'
               INTO v_listmsg
          SEPARATED BY space.
      ENDIF.
      WRITE: / v_listmsg.
      WRITE: /3 '--', v_msg.
      syst-subrc = v_rc.
    ENDIF.
ENDIF.
ENDFORM.
      FORM CLOSE_DATASET                                            *
Closes dataset                                                      *
--> VALUE(P_FILE) Name of the file to be closed                  *
FORM close_dataset USING value(p_file) TYPE unixfile.
CLOSE DATASET p_file.
ENDFORM.
*&      Form check_input_data
This subroutine is used to check the data from X Ref files
FORM check_input_data.
DESCRIBE TABLE tbl_matnr LINES v_count.
Use the material conversion routine to pad the material numbers
with zeroes
LOOP AT tbl_matnr.
    CALL FUNCTION 'CONVERSION_EXIT_MATN1_INPUT'
         EXPORTING
              input        = tbl_matnr-matnr
         IMPORTING
              output       = tbl_matnr-matnr
         EXCEPTIONS
              length_error = 1
              OTHERS       = 2.
    TRANSLATE tbl_matnr-matnr TO UPPER CASE.
    MODIFY tbl_matnr.
ENDLOOP.
Get the materials from SAP database using the input materials
IF NOT tbl_matnr[] IS INITIAL.
    SORT tbl_matnr BY matnr.
    SELECT matnr FROM mara
      INTO TABLE tbl_mara
       FOR ALL ENTRIES IN tbl_matnr
     WHERE matnr = tbl_matnr-matnr.
    SORT tbl_mara BY matnr.
ENDIF.
Check the existence of input materials in SAP database
LOOP AT tbl_matnr.
    READ TABLE tbl_mara WITH KEY matnr = tbl_matnr-matnr
         BINARY SEARCH.
    IF sy-subrc <> 0.
      CONCATENATE 'Material' tbl_matnr-matnr 'does not exist'
             INTO tbl_error-error_text
        SEPARATED BY space.
      APPEND tbl_error.
      CLEAR tbl_error.
      DELETE tbl_matnr.
    ENDIF.
ENDLOOP.
ENDFORM.                               " check_input_data
*&      Form get_sd_sa_data
This subroutine is used to get the SD Scheduling data from database
FORM get_sd_sa_data.
*begin of changes - DN3K923909
DATA: tbl_vbep LIKE tbl_vbep_forecast OCCURS 0 WITH HEADER LINE,
        tbl_vblb LIKE tbl_vblb_forecast OCCURS 0 WITH HEADER LINE.
*end of changes - ND3K923909
REFRESH: tbl_vbap_vapma, tbl_vbpa, tbl_vblb_forecast,
           tbl_vblb_jit, tbl_vbep_forecast, tbl_vbep_jit.
CLEAR:   tbl_vbap_vapma, tbl_vbpa, tbl_vblb_forecast,
           tbl_vblb_jit, tbl_vbep_forecast, tbl_vbep_jit.
Get the Scheduling Agreements
SELECT avbeln aposnr
       a~vgbel
         AAUART avkorg avtweg aspart a~kunnr
        a~ablfz
         A~MATNR
       a~pstyv
         a~werks
       a~lgort
        a~vstel
          ATRVOG BVBTYP BVSBED BBSTNK B~KTEXT
    FROM VAPMA AS A INNER JOIN VBAK AS B
      ON bvbeln = avbeln
    INTO TABLE tbl_vbap_vapma
     FOR ALL ENTRIES IN tbl_mara
   WHERE a~matnr = tbl_mara-matnr
Begin of Changes - TIR-40266
     AND a~vkorg IN s_vkorg
     AND a~werks IN s_werks
End of Changes - TIR-40266
     AND A~TRVOG = '3'
     AND B~VBTYP IN S_VBTYP.           "Murali Poli
    and a~abgru = ''
    and b~gueen >= p_gueen.
SORT tbl_vbap_vapma BY vbeln posnr.
IF NOT tbl_vbap_vapma[] IS INITIAL.
    SELECT VBELN POSNR VGBEL ABLFZ PSTYV LGORT VSTEL FROM VBAP
     INTO TABLE TBL_VBAP FOR ALL ENTRIES IN TBL_VBAP_VAPMA
       WHERE VBELN = TBL_VBAP_VAPMA-VBELN
        AND POSNR = TBL_VBAP_VAPMA-POSNR.
    LOOP AT TBL_VBAP_VAPMA.
      READ TABLE TBL_VBAP WITH KEY VBELN = TBL_VBAP_VAPMA-VBELN
                                   POSNR = TBL_VBAP_VAPMA-POSNR.
      IF SY-SUBRC = 0 .
        TBL_VBAP_VAPMA-VBELN = TBL_VBAP-VBELN.
        TBL_VBAP_VAPMA-POSNR = TBL_VBAP-POSNR.
        TBL_VBAP_VAPMA-VGBEL = TBL_VBAP-VGBEL.
        TBL_VBAP_VAPMA-ABLFZ = TBL_VBAP-ABLFZ.
        TBL_VBAP_VAPMA-PSTYV = TBL_VBAP-PSTYV.
        TBL_VBAP_VAPMA-LGORT = TBL_VBAP-LGORT.
        TBL_VBAP_VAPMA-VSTEL = TBL_VBAP-VSTEL.
        MODIFY TBL_VBAP_VAPMA .
      ENDIF.
    ENDLOOP.
    tbl_vbap_vapma_temp[] = tbl_vbap_vapma[].
*--Begin of UnCommentDIR-51476-DN3K932648
-------------- Begin of Comment ----------- CCR-50124 DN3K928457
    SORT tbl_vbap_vapma_temp BY vbeln.
    DELETE ADJACENT DUPLICATES FROM tbl_vbap_vapma COMPARING vbeln.
-------------- End of Comment ----------- CCR-50124 DN3K928457
*--End of UnCommentDIR-51476-DN3K932648
*--Begin of CommentDIR-51476-DN3K932648
-------------- Begin of Insert ----------- CCR-50124 DN3K928457
Duplicate Line Items are being deleted.
   SORT tbl_vbap_vapma BY vbeln posnr.
DELETE ADJACENT DUPLICATES FROM tbl_vbap_vapma COMPARING vbeln posnr.
The field for contract in SA is being modified for uniqueness
   loop at tbl_vbap_vapma.
     clear: v_vgbel, v_posnr.
     v_vgbel = tbl_vbap_vapma-vgbel.
     v_posnr = tbl_vbap_vapma-posnr.
     if not v_vgbel is initial .
       shift v_vgbel left deleting leading v_zero.
       shift v_posnr left deleting leading v_zero.
       v_posnr = v_posnr / 10.
       condense: v_vgbel, v_posnr.
       if v_posnr le 9.
         concatenate v_vgbel '0' v_posnr into v_vgbel.
       else.
         concatenate v_vgbel v_posnr into v_vgbel.
       endif.
     endif.
     tbl_vbap_vapma-vgbel = v_vgbel.
     modify tbl_vbap_vapma.
   endloop.
-------------- End of Insert ----------- CCR-50124 DN3K928457
*--End of CommentDIR-51476-DN3K932648
Get the Partner details
   select vbeln posnr parvw kunnr
*Start of Murali Poli
    SELECT VBELN POSNR INCO1 INCO2
           INTO TABLE TBL_VBKD
           FROM VBKD
           FOR ALL ENTRIES IN TBL_VBAP_VAPMA
           WHERE VBELN = TBL_VBAP_VAPMA-VBELN.
          and posnr = tbl_vbap_vapma-posnr.
*End of Murali Poli
    SELECT vbeln posnr parvw kunnr lifnr                    "DN3K923909
      INTO TABLE tbl_vbpa
      FROM vbpa
       FOR ALL ENTRIES IN tbl_vbap_vapma_temp
     WHERE vbeln = tbl_vbap_vapma_temp-vbeln
       AND parvw IN ('WE', 'SP').
*begin of changes - DN3K923909
   select vbeln posnr abart abefz labnk abrdt gjkun vjkun
     into table tbl_vblb_forecast
     from vblb
      for all entries in tbl_vbap_vapma
    where vbeln = tbl_vbap_vapma-vbeln
      and posnr = tbl_vbap_vapma-posnr
      and abrli = '0000'
      and abart = '1'.
    SELECT vbeln posnr abart abefz labnk abrdt gjkun vjkun
      INTO TABLE tbl_vblb
      FROM vblb
       FOR ALL ENTRIES IN tbl_vbap_vapma
     WHERE vbeln = tbl_vbap_vapma-vbeln
       AND posnr = tbl_vbap_vapma-posnr
       AND abrli = '0000'
       AND abart IN ('1','2').
    SELECT vbeln posnr etenr edatu ezeit wmeng prgrs abart
      INTO TABLE tbl_vbep
      FROM vbep
       FOR ALL ENTRIES IN tbl_vbap_vapma
     WHERE vbeln = tbl_vbap_vapma-vbeln
       AND posnr = tbl_vbap_vapma-posnr
       AND abart IN ('1','2').
Get the current Forecast delivery schedule
    tbl_vblb_forecast[] = tbl_vblb[].
    DELETE tbl_vblb_forecast WHERE abart = '2'.
Get the current Forecast Schedule lines
    tbl_vbep_forecast[] = tbl_vbep[].
    DELETE tbl_vbep_forecast WHERE abart = '2'.
Get the current JIT delivery Schedule
   select vbeln posnr abart abefz labnk abrdt gjkun vjkun
     into table tbl_vblb_jit
     from vblb
      for all entries in tbl_vbap_vapma
    where vbeln = tbl_vbap_vapma-vbeln
      and posnr = tbl_vbap_vapma-posnr

Sales Order / Forecasted Sale Order Report

hi
How to create Sales Order / Forecasted Sale Order Report.

Hi Raju,
Are you talking of normal sales order and in the Forecasted sale order report what are the inputs you are giving.

Linking between Sales order data and Biling condition

Hi Bwers,
Currently we are geneating a report with Sales order Item level (2lis_11_VAITM) information and Biling conditions(2lis_13_VDKON). We have respective DSO for both datasources (Sales order DSO and Biling Condition DSO). We have to pull both information into a report.
We have sales order number (0DOC_NUM) in Sales DSO and Biling document number (0BILL_NUMber) in Biling DSO. And we found Sales order Number (0BILL_NUM_0DOC_NUMB) as an navigational attribute for Biling DSO.
We are trying to extract Billing condition type and Billing condition value from Billing DSO.
Now the question's are:
1. Can I use Sales order number as linking field for Both DSO' or not. Though It is an Navigational attribute for Biling document number in Biling DSO.
2. Is the Sales order number and Billing Document number both are same or not. What is the linking field between sales order info to Biling info.
2. How to bring Sales order info and Biling info into a report through Infoset. If infoset which link should I use bring both info into a report.
3. Or Multiprovider is the right one.
3. Please let me know if any other linking fields are existed between these two datasources other than Sales order.
All the helpful answers are awareded with full points.
Regards,
Venkat

1. Can I use Sales order number as linking field for Both DSO' or not. Though It is an Navigational attribute for Biling document number in Biling DSO.
- yes you can link, Navigation attrbute does not matter
2. Is the Sales order number and Billing Document number both are same or not. What is the linking field between sales order info to Biling info.
--one sales order number may correspond to different billing number including the one which shares the same number.
2. How to bring Sales order info and Biling info into a report through Infoset. If infoset which link should I use bring both info into a report.
-- Multiprovider is the best option while dealing with such cases.
3. Or Multiprovider is the right one.
--yes.
3. Please let me know if any other linking fields are existed between these two datasources other than Sales order.
there may be possibilty of other fields also like Profit center, Controling area etc depending upon your project requirment

UI: Opening Sales Order screen and loading with data

Hi,
I'm currently using the SDK to develop a new screenin SBO. From my new screen I need to display the sales order screen with an order loaded into it.
I currently open the screen using the ActivateMenuItem methid, then use the sendKeys method to try and change to find mode, pass in the sales order number and press enter to start the search.
The code is this:
moSBOApp.ActivateMenuItem("2050");
moSBOApp.SendKeys("(^f)");
moSBOApp.SendKeys("123");
moSBOApp.SendKeys("{ENTER}");
But the form doesn't seem to change modes, it just stays in "Add" mode. Is there a better way of doing it?
I've also tried putting code in the FORM_LOAD event for the sales order screen and try and change mode then, but I just get an "Invalid Form Mode" error
Help!

Ho Jon!
The following snippet works fine for PO searching by number and date:
SAPbouiCOM.Form          frmPurchOrd = null;
int frmPOCount = 0;
SAPbouiCOM.EditText     oOrdNum;
SAPbouiCOM.EditText     oOrdDate;
SAPbouiCOM.Item          oOrdOkButton;
SBOApp.ActivateMenuItem("2305");
// PO even opened
for (int k=0; k<SBOApp.Forms.Count; k++)
     if (SBOApp.Forms.Item(k).Type == 142)
          frmPOCount++;
frmPurchOrd     = SBOApp.Forms.GetFormByTypeAndCount(142, frmPOCount++);
frmPurchOrd.Freeze(true);
frmPurchOrd.Mode = SAPbouiCOM.BoFormMode.fm_FIND_MODE;
oOrdNum          = (SAPbouiCOM.EditText)frmPurchOrd.Items.Item("8").Specific;
oOrdNum.String     = OrdNum;
oOrdDate     = (SAPbouiCOM.EditText)frmPurchOrd.Items.Item("10").Specific;
oOrdDate.String     = OrdDate.ToShortDateString();
oOrdOkButton     = (SAPbouiCOM.Item)frmPurchOrd.Items.Item("1");
oOrdOkButton.Click(SAPbouiCOM.BoCellClickType.ct_Regular);
frmPurchOrd.Freeze(false);
it's too easy to implement it for Sales Order

Do you know the link between the sales order item and functional location ?

How know the functional location if I know de sales order number and item ?
Wich table or bapi ?
Tks.

Hi,
I think there's all details in my question.
You answer is right only if I need to know the functional location at AUFNR level.
Is not my case, I need this information at sales order level.
Regards,
Roberto.

Reg Open sales order item and the quantity

Hi experts:
I am getting open sales order item based on inner join of tables(vbak, vbap, vbep). Not using vbbe table in inner join as it doesnt carry all pending open records.
can any one say how open sales order items and their quantity can be retrieved?
I searched forum and saw usage of vbuk and vbup tables, but it does not accomplish our scenario.
Thanks in advance,
Sashti.

Hi,
1) fetch the header information from VBAK table.
2) Based on VBAK table fetch all the line items from VBAP table.
3) Now fetch from VBFA table.
*-Fetch from VBFA to get the delivered qty
SELECT vbelv               " Preceding sales and distribution document
         posnv               " Preceding item of an SD document
         rfmng               " Referenced quantity in base UOM
    FROM vbfa
    INTO TABLE lt_vbfa
     WHERE vbelv   = gv_vbeln
       and vbtyp_n = 'J'.
4) By comparing VBFA-POSNR just filter the records from the VBAP internal table. Remained lines are open lines of the sales order.
Regards,
~Satya

How to compare sale order bom and production order bom.

i would like to provide report with respect to comparation of sale order bom and production order bom, but i am not familiar with SD and PP, can anyone give me some clue? i only know sale order bom is created via 'CS61', afterwards run mrp to get production order, the process appears complicated, i needn't know the process detail, just want to know how to get sale order bom and relative production order bom. please guide me.

Hi,
Check Tcode:CS14 to SD/PP BOM's
Chidambaram

Reinitialize Sales Orders, Billing and Delivery (11, 12 & 13)

Hi,
Due to continues rollouts we need to reinitialize Sales Orders, Billing and Delivery do-cuments from R/3 into BW.
This requires us to delete all loaded data, logs, queues etc. on the BW side - Fair enough.
The real challenge come as we need to run the transactions OLI7BW(order), OLI8BW (billing), OLI9BW (deliveries) on the R3 side in order to fill the setup tables. Here we need to switch the "block all orders" on in order to ensure that no new documents are created while load-ing.
In relation to the above situation I have a couple of questions:
Is there no way of doing this in a more "online" fashion?
What transactions are actually blocked by flicking the "block all orders"?
Thanks in advance
Michael Bisfelt
Arla Foods a.m.b.a
Message was edited by: Michael Bisfelt

Hi Michael,
I've seen this process accomplished without blocking orders, but instead by blocking all transactions that may in any way lock an order or related sales document. Also, you can dramatically speed up the process of gathering the old documents by running multiple batch jobs (with different document number ranges) at the same time. In this case, I believe you want to "uncheck" the "New run" flag. I've seen runtimes for this reduced from over 24 hours to under 4 hours. The important thing is that you don't want to have ANY activity that modifies or locks order documents until after the date and time of termination that you specified, otherwise you will lose data on your transfer to BW.
Regards,
Chris

What is the relation between delivery num , sales order num and invoice

what is the relation between delivery num , sales order num and invoice

Look at VBFA Table
goto VBFA table ,enter order number number vbelv ,vbtyp_n is C,then VBELN is the delivery
if you enter delivery number in vbelv ,vbtyp_n is J,then vbeln is Invoice.
here VBTYP_N is the import.
VBFA is the sales document flow table,and very important table
Thanks
seshu

How to trigger an Idoc from Sales order creation and change

We are trying to trigger Idoc from sales order creation and change we have done following setting mentioned below:
Follow the below steps:
1. Go to NACE transaction
2. Select V1 application and select OUTPUT TYPES
3. Select the required output type and double click on Processing routines.
4. Enter Medium as DISTRIBUTION ALE, Program as RSNASTED and Routine as ALE_PROCESSING.
5. Save it.
message type ORDERSP in the distribution model (BD64).
Follow the below steps to configure the condition records:
1. Go to NACE
2. Select V1 application and select CONDITION RECORDS
3. Select the requred output type and click on Condition records
4. Selection screen will be displayed.
5. Go for execution. In that screen enter the selection criteria. For eg Condition record is based on Sales document type. Then
Sales doc type = OR
Funt = SP
Partner = blank. It means there is no restriction on partner numbers.
Medium = A
date/time = 4
Lan = EN.
Note: partner is left blank means, the sales order of type OR can be send to all partners.
6. Save it.
We also done ALE configuration.
We are facing problem that from VA02 "No output has been selected for printing Message no. V1102"
Kindly suggest the solution.
Regards,
Sharad Dixit

Hi ,
Please check the total error description and diagnosis as below :
InVa02 enter SO go to extras->output->Header->edit.You can find a table with all the triggered output types. Choose the output type BA00 with medium Distribution ALE and go for 'Processing log'. It will show you the error description.
Please paste the diagnosis .
Thanks and Regards,
P.Bharadwaj

Sales order no and line item no in account assignment tab of line item no.

Hi All,
When we display a sales order and go to line item --> Account assignment tab --> we can see sales order no and line item no in that screen. We want to know from where this existing no. in that field is populating from.
We want to know this as we want to check feasibility of changing sales order and item no to maintenance contract no and line item no. ( Maintenance contract we have to pick from notification)
If anybody has any idea about this do let me know as this is urgent requirment.
Effort will be rewarded.
Thanks in advance.
Edited by: Satish Bharambe on Jul 4, 2008 10:38 AM

Hi Satish,
You mean Accounting assignment tab-->In Settlement rule details
If yes the order number which is coming in that field Sales order and for which sale order you are looking that details both are the same numbers(i.e Nothing but sales order number).
When you create sales order system will give number of the sales order the number will come in this place.
I hope it will help you,
Regards,
Murali.

Fetch Sales order number and PO number from ship to party and sold to party

HI,
I need to get Sales order number and PO number
from ship to party and sold to party.
I have only ______sold to party and ship to party and req del date_______ in selection screen as mandatory
Please let me know
Sreekanth

Hi,
You can do this:-
SELECT VBELN FROM LIKP
INTO TABLE T_DELIVERIES
WHERE KUNNR = SHIP TO PARTY
AND     KUNAG = SOLD TO PARTY
AND LFDAT      = DEL DATE.
You will get a table containing the list of deliveries.
Use VBFA to get the sales orders from deliveries.
SELECT VBELV FROM VBFA
INTO TABLE T_SALESORDERS
WHERE VBTYP_N = 'J'
AND     VBELN = T_DELIVERIES-VBELN.
T_SALESORDERS WILL give you list of sales orders.
From Sales Orders you can get Purchase orders through EKKN Table.
Using EKKN pass T_SALESORDERS-VBELN and get corresponding EBELN.
Regards,
SUbhashini

External system Sales Order no and Line Item no in to BAPI_HU_CREATE

Hi Friends
Packing is done and Handling units are created in External System.
For this requirement SAP ECC has to update Handling Units creation and Materials Packing in to HU with reference External System Sales Order no and Line Item no.
Could you please advice how & where to input External system Sales Order no and Line Item no in to BAPI_HU_CREATE Function Module while creating Handling Units in SAP ECC system.
Thanks in Advance.
SR

Hi Guru
Please help on this requirement.
Thanks
Ravi

Relationship table of Sales Order (VA03) and Delivery Order (VL03N)

Hi everyone!
What table can I see the relationship of Sales Order document (VA03) and Delivery Order document (VL03N) as shown in VA03 > Environment > Document Flow?
I mean, what tables saves the partnerships of each document (query sales order no. and get equivalent delivery order no. or nos.)
Thank you very much!

Hi
U can use the fm RV_ORDER_FLOW_INFORMATION in order to get out those links or you can read the item table LIPS:
LIPS-VGBEL = sales order number
LIPS-VGPOS = salese order item
Max

ISupplier Forecasting, sales order demand and current INV levels?

Similar Messages

Maybe you are looking for