Intresting problem and Sales order Date...

We have a nice problem if u want to see we have created a Sales order at 10 am. Intrestingly it says that Sales order XXXXXXXXXX has been created at 10 am and changed at 9 am. Does anyone know why its pulling the wrong information?? Please let me know how this can be solved
Best regards,
Lata.

Hi latha,
This might be the problem with time zone assigned to different users.
Can you check th time zone of the user who created the order & the time zone of the user who changed the order.
Regards
Arun Kumar

Similar Messages

Delivery date and sale order dates

Hi
Requested delivery date is 13th sep
Commitment date is 14th sep
Confirmed date is 21st sep
PGI date is 21st sep
1. But delivery creation date in 18th sep ..How?
2. How system determine the commitment date
Find below screen shots
VOV8 contain commitment date as "B"

if the org feels this is important then it cancells another delivery and that stock is to be delivered to the urgent customer. after u have to deliver the stock to the other customer. Other wise we have to deliver intially whatever stock we have with us and go to back order processing then deliver the remaining

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.

Sales order and purchase order date management

Hi all,
I am new to SAP so please pardon the question in advance if this is a basic one.
I need a little help with purchase order and sales order dates. Our supplier runs SAP and our two systems are tied together. Currently my supplier is not updating their promise date because this is how we are tracking late shipments. However, this means ETA/ETD dates are incorrect. Is there a way for us to keep track of late shipments and still maintain accurate ETD/ETA dates? Thanks in advance for any help you can provide!

Firstly, thank you Edgar and Rahul for taking the time to answer my question.
Apologies guys I should have provided more information in my initial post.
Our parent company is also our supplier. We cut a purchase order, notify them of the purchase order and in turn they cut a sales order. My supplier (parent company) is stating if they update the "first date" column in their sales order (which would in turn populate a correct ETA date) we will lose the ability to track late shipments.
To answer your question Edgar I am referring to the sales document. It is my understanding my supplier is only modifying the "First Date". Are there several date field in a sales document we can use to 1. track original promise date 2. maintain accurate ETA?
From a "customer" standpoint I need to be able to view both dates so that I know when I can expect to actually receive product and if that product is/was late.
Thanks!

Problem about sales order stock stock transfer and batch determination

Hi, experts, I get a problem about sales order stock stock transfer and batch determination.The following is the current situation of my system:
In OMCG I assigned search procedure ME0001 to both 311 and 311 E and ticked check batch. After that, I found that if iI need to tranfer unrestricted-use material from storage location 1000 to 2000 with movement type 311, I just need to input * at the field batch, then the system will display all of the available batches. But for the transferring of sales order stock with movement type 311 E, after I input * at the batch field, no batch is displayed and there is also no message from the system.
Can anybody help me? Is there anything else I need to do? Thanks very much.

I think my question is not clear, actually I tried 562 E , 411 E and 413 already. all the transaction looking for the sales order but unfortunatly the sales order is deleted from SAP.

BAPI for Create PO from Sales Order Data and POST GR from PO created

Dear,
         Can u help me how to create BAPI for Purchase Order creation from sales order Data
          what the bapi to Post GR from the PO created.
Regards,
Manoj

Hello Manoj what you have to do to create PO from PR is that
1) Use   BAPISDORDER_GETDETAILEDLIST (pass sales order number in sales_document table) and then get PR (Purchase requisition number from this BAPI.
2) Use BAPI_REQUISITION_GETDETAIL to get PR items
3) Use BAPI_PO_CREATE1 to craete PO from PR then.
to create goods movement you can use
BAPI_GOODSMVT_CREATE
REWARDS IF USEFUL.

Fetching the sales order data using both system status and user status

Hi,
Could any one tell me how to fetch sales orders using both system status and user status.
My requirement is to fetch sales order data in a report where the user enters the system status and user status in the selection screen fields.
For example i need sales orders where the system status is I1002 i.e. OPEN and user status is E0002 (status profile CMSCON0) that is In Process
Early replies are appreciated.
Thanks
Tanveer

Hi,
The system status and user status are stored in CRM_JCDS & CRM_JEST tables you can get the all the order GUID on particular status further pass the order GUID in table CRMD_ORDERADM_H to get transaction ID.
Regards,
Dipesh.

Problem with sales order and Service order

Dear Guru's
We have a real problem with sales orders and service orders and how we treat these. For a project that uses a WBS, it's not a problem to manipulate SAP to give us a list of shortages (orders with no or limited supply) for each order, but for some reason our after sales orders and our service orders do not work this way.
Thanks and Regards,
Deethya.

CLOSED

Sales Order Date and Despatch Advice Date

Hi all,
I need to create a view that contains Sales Order #, Despatch Advice # , Sales Order Date, Despatch Advice Date and Sales Organization. Please tell me that using which tables, required view can be created?
Regards,
AI.

In table VBAK, you can take the fields Sales Organisation, po # & Date.
What do you mean by Despatch Advice # ?? If you are referring to delivery which we generate in VL01N, you can make use of table LIKP for header level and LIPS for item level.
thanks
G. Lakshmipathi

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

Purchase orders and Sale Orders in DEV and PRD

Hi SAP Experts,
We have a facing some different problem. Unfortunately our clint do some transactions in Development Server. Like Purchase orders and Sales Orders.
After one month we delivery to clinet exact Production server. But he is asking , What ever the purchase orders and Sales Orders Created in Development with same numbers and Same dates, that data will be present in Production server also. Is it possible to do that. IF possible how to do that...
Thanks and Regards
Siri....
Edited by: Alvaro Tejada Galindo on Apr 14, 2008 5:56 PM

I think it is possible,as per my knowlwdge our perious client regularly( means every 3-4 months) copied the data from Production server to quality server. by the help of basic person...
So in your case you want to copied the data from devlopment server to production server....please touch with your basic guy, i think he will help out reagrding this...

Condition Period Problem in Sales order - Need help

Hi Gurus
I am testing Sales Order back dated
Condition period Problem in Sales order
example for you to understand
Sales Order where PO date is 17.12.2007
Del Date & Price date is 13.02.2008
Then it is not calculating IN: A/R BED %IN A/R BED totalN A/R CESS [1621]
But if i do it after 14 feb 2008 then it is calculating IN: A/R BED %IN A/R BED totalN A/R CESS [1621]
When I do it with current date it is calculating IN: A/R BED %IN A/R BED totalN A/R CESS [1621] say date is 9-5-2008
I am not able to trace out problem, kindly help me from where I do I check and why this is happening.
Rajesh Chalke

Hi,
I am not sure if this solves your problem, but I am suspecting that this might be due to the 'valid on date' of the condition records created for the relevant duty condition types.
Since it was a recent regulation and VK11 usually defaults current date as the valid date, that condition record may have been valid only from the recent date on which it was created.
Check the date in VK12 (To find the exact selection parameters, check the pricing analysis in the sales order which will display the exact condition record which is being selected as of current date.) Check for the same parameters; change the date to relevant date in the past and recreate the sales order. Hopefully this should solve the issue.
Cheers,
KC

BAPI - Problem in Sales order creation

Hi Friends,
I have problem in Sales order creation using BAPI ,I am getting a messsage - Error in creating document ,I have sent the code along with this mail ,can you help it out.
Code:
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
PARAMETERS: p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Sales organization
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Distribution channel
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Division.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Sold-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Ship-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Material
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Quantity.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Plant
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Data declarations.
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead1.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapisditem OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                         WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                         WITH HEADER LINE.
Initialization.
INITIALIZATION.
v_text   = 'Order type'.
v_text1 = 'Sales Org'.
v_text2 = 'Distribution channel'.
v_text3 = 'Division'.
v_text4 = 'Sold-to'.
v_text5 = 'Ship-to'.
v_text6 = 'Material'.
v_text7 = 'Quantity'.
v_text9 = 'Plant'.
Start-of-selection.
START-OF-SELECTION.
Header data
Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
Partner data
Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
Ship to
partner-partn_role = 'WE'.
partner-partn_numb = p_ship.
APPEND partner.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
Call the BAPI to create the sales order.
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
       EXPORTING
            sales_header_in     = header
            sales_header_inx    = headerx
       IMPORTING
            salesdocument_ex    = v_vbeln
       TABLES
            return              = return
            sales_items_in      = item
            sales_items_inx     = itemx
            sales_schedules_in = lt_schedules_in
            sales_schedules_inx = lt_schedules_inx
            sales_partners      = partner.
Check the return table.
LOOP AT return WHERE type = 'E' OR type = 'A'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0.
    WRITE: / 'Error in creating document'.
ELSE.
Commit the work.
    COMMIT WORK AND WAIT.
    WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF.
Regards,
Dinesh

what messages u are gettting in RETURN ? Please check the RETURN tables data.
[code]CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
EXPORTING
sales_header_in = header
sales_header_inx = headerx
IMPORTING
salesdocument_ex = v_vbeln
TABLES
return = return
sales_items_in = item
sales_items_inx = itemx
sales_schedules_in = lt_schedules_in
sales_schedules_inx = lt_schedules_inx
sales_partners = partner.
Regards
Prabhu

How to transfer Sales order data from R/3 to APO!!

Hi Techies,
I am in the process of moving some sales order data for a particular mat/loc combination in cfm1 after creating a integration model iam even activating even in R/3 but after doing this iam not able to view those sales orders in RRP3 t-code IN APO side.
Kindly let me know what is the procedure to transfer transactional data from R/3 to APO and to do enhancement in CIF which carries Transactional data .
Problem solving answers would be rewarded duly !!.
+PKP.

Hi PKP,
The field SPEC_STOCK has the description "Key for Special Stock Section" and is linked to schedule line of the PO. This seems to be something linked to special stock, but I am not very sure about the relevance of this field.
I do not see any related field when I check the order in RRP3 or in RRP2. In standard SAP, you would only be able to use the fields that are already visible in APO. Otherwise you need to add the field to the standard SAP t-code display (read the value from SOMEWHERE and then display it in RRP3. This is possible using Badi /SAPAPO/RRP_IO_COL). Then only you can see the values which you have populated.
If this field SPEC_STOCK already has some functionality (which it should have, though I am not sure what it is), you might not be able to use it for other purposes (since system does some validations for certain fields).
You are updating the value for this field in IT_OUTPUT internal table, you also need to add an X in the corresponding field in the internal table IT_OUTPUTX.
You could try putting this X, so that your changes are considered in CIF, but I am not sure what the impact may be, and you could get a dump also possibly. Even otherwise, since this field doesn't seem to be visible against a PO in APO, I am not sure if this would be helpful for you.
As far as I could see, I did not find any standard field which could be helpful for you.
May be if you open a fresh thread and ask for advice on how to send any custom comments for PO to APO, someone could provide some inputs.
Thanks - Pawan

Combined Purchase Order and Sales Order Query. (Including Stand Alone Docs)

Hi,
I need some help please!
I am looking for a query that will show all the Purchase Orders with all their base document Sales Orders. However I also need to show those stand alone Purchase orders and Sales Orders.
What I have is two queries, one for the PO fields en one for The SO fields. I would like a way to combine these two so I have one query with the relevant PO and SO info next to each other.
The final query will have a top heading structure like this:
Status,Purchase No.,Supplier No.,Supplier Name,Week,Month,Del Method,Country,Method,Rep.|Status,Rep.,Sales No.,Customer No.,Customer Name,Customer Order no.,Cust. Del date,Doc total,Del Method
+(The first part is for the purchase order section, the second part starting at the second 'Status' is the sales order section)
+Purchase Order Query:
SELECT
T0.DocStatus 'Status',
T0.DocNum'Purchase Order No.',
T0.CardCode 'Supplier No.',
T0.CardName'Supplier Name',
DATEPART(ww,T0.DocDuedate)'Week',
DATEPART(mm,T0.DocDuedate) 'Month',
T1.TrnspName 'Delivery Method',
T2.Country 'Country',
T0.JrnlMemo 'Method',
T3.SlpName 'Rep.'
FROM OPOR T0
INNER JOIN OSHP T1 ON T0.TrnspCode = T1.TrnspCode
INNER JOIN OCRD T2 ON T0.CardCode = T2.CardCode
INNER JOIN OSLP T3 ON T0.SlpCode = T3.SlpCode
Sales Order Query:
SELECT
T0.DocStatus 'Status',
T2.SlpName 'Rep.',
T0.DocNum 'Sales Order No.',
T0.CardCode 'Customer No.',
T0.CardName 'Customer Name',
T0.NumAtCard 'Customer Order no.',
T0.DocDueDate 'Cust. Delivery date',
T0.DocTotal ' Doc total',
T1.TrnspName ' Delivery Method'
FROM ORDR T0
INNER JOIN OSHP T1 ON T0.TrnspCode = T1.TrnspCode
INNER JOIN OSLP T2 ON T0.SlpCode = T2.SlpCode
The problem I am having is that if I combine these queries it excludes all those records with blank/empty data fields.
I do not mind having to go to crystal reports to get what I want.
Any suggestions?
Thanks!

Hi thanks GordonDu,
I have tried a union before, and yours works great. However my problem is to display the PO en SO columns next to each other and not underneath each other.
Something like this:
Po No          Supplier          SO No           Customer
1234           Sup 1             9876              Cust 1
1235           Sup 2             no SO             Cust 2
1236           Sup 3             9877              Cust 3
1237           Sup 4             9878              Cust 4
1238           Sup 5             no SO             Cust 4
I have this query, but with this it drops all those Purchase Orders made Stand Alone and without a SO number.
SELECT
T2.DocNum AS 'Purchase Order No.',
T0.DocNum AS 'Sales Order No.',
T2.CardCode AS 'Supplier No.',
T2.CardName AS 'Supplier Name'
FROM ORDR T0
   INNER JOIN RDR1 T1 ON T0.DocEntry = T1.DocEntry
   INNER JOIN OPOR T2 ON T2.DocEntry = T1.PoTrgEntry
Though using your Union gives me all the information I want and the ability to expand on that, my problem is the "Display" part. I am sure I am doing something stupid somwhere
Edited by: Desmond Moll on Mar 7, 2012 8:03 AM

Intresting problem and Sales order Date...

Similar Messages

Maybe you are looking for