Screen compression problems in sales order additional data b screens

When i enter va01 for the slaes order he screens are:
SAPMV45A8309, Sales Document Header - User Exit Header
SAPMV45A8459, Sales doc. Item - User exit item
Use screen painter to change them. (transaction SE51)
what happened is that i have four boxes in additional data b subscreens and i am calling another sub screen 9801 which contains table control what happened is that while run time i am getting gap in the boex of screen 8459, how to compreess the boxes or spaces to accomodate the table control.
very urgent pls.....
regards
subba

Thanks for your reply , Actually i am calling  9801 sub screen  with table control on to 8459 sub screen(sapmv45a program)
still the problemm remains the same. I am using the code as below.zie,z01,zia are all modification groups to hide the boxes in the 8459 screen, pls check my code and revert back   urgently urgently.....
PROCESS BEFORE OUTPUT.
                           Verarbeitung vor der Ausg
    MODULE ZZ_GET_TEXT.
   MODULE ZZ_FIELD_SETTINGS.
  CALL SUBSCREEN ZZAUDIT INCLUDING 'SAPMV45A' '9801'.
PROCESS AFTER INPUT.
   CALL SUBSCREEN ZZAUDIT.
MODULE    ZZ_FIELD_SETTINGS OUTPUT.
  LOOP AT SCREEN.
  Determine main grouping based upon mod group 3 field.
    CASE SCREEN-GROUP3.
      WHEN 'ZIA'.                    " Orbit  /interface architecture.
        PERFORM ZZ_FIELD_ZIA.
      WHEN  'ZIE'.                  " ERI interface.
        PERFORM ZZ_FIELD_ZIE.
      WHEN 'Z01'. " Generic -Relevant for all interfaces potentially.
        PERFORM ZZ_FIELD_Z01.
    ENDCASE.
  Handle display of contract versus other doc types.
    IF VBAK-VBTYP EQ  'G'.       "Contract doc type.
      IF SCREEN-GROUP4 NE  'Z02'.
        SCREEN-ACTIVE = 0.  " field not relevant for contract display.
      ENDIF.
    ELSE.                    "other doc types.
      IF SCREEN-GROUP4 EQ 'Z02'.
      Field not relevant for non-contract display.
        SCREEN-ACTIVE  = 0.
      ENDIF.
    ENDIF.
FORM ZZ_FIELD_ZIE.
  IF NOT VBAK-AUART IN ZZR_AUART.
IA related Doc Type - Hide ERI fields
    SCREEN-ACTIVE = 0.
  ELSE.
  IF SY-BINPT NE 'X'.         " Not Processing in BDC Mode
    SCREEN-INPUT = 0.         " Turn Off Input Ability
  ENDIF.
    CASE SCREEN-GROUP4.
      WHEN 'ZAU'.                " Audit Toggle Related
       IF zzshowaudit NE 'X'.
         screen-active = 0.
       ENDIF.
      WHEN 'ENA'.
        SCREEN-INPUT   = 1.
      WHEN 'ZTS'.
        IF SY-SYSID EQ 'DV2'.
          SCREEN-INPUT = 1.      " Testing Allowed in Development
        ENDIF.
    ENDCASE.
  ENDIF.
FORM ZZ_FIELD_ZIA.
  IF VBAK-AUART IN ZZR_AUART.
  ERI related Doc Type  -Hide IA related fields
    SCREEN-ACTIVE = 0.
  ELSE.
    CASE SCREEN-GROUP1.
      WHEN '001'.                             "0902 specific fields
      WHEN '002'.                              "0902 WebCore fields
        IF  VBAK-VKORG NE '0902' AND
            VBAK-VKORG NE '0903' AND
            VBAK-VKORG NE '0917'.
          SCREEN-INPUT = 0.
        ENDIF.
      WHEN '003'.                              "0917 specific fields
        IF VBAK-VKORG NE '0917'.
          SCREEN-INPUT = 0.
        ENDIF.
      WHEN '999'.                             "Generic Fields
        IF VBAK-VKORG EQ '0917' OR
           VBAK-VKORG EQ '0902' OR
           VBAK-VKORG EQ '0903'.

Similar Messages

  • Sale Order additional data B.

    Hi,
    I have created 2 z fields in sale order additional data b at item level.
    but when user is entering any data in that field,same data is getting displayed for all line items.
    how to control that for particular item for which user has entered.
    Data Entered in z fields are used only for display purpose which are used for some calculations.

    hi,
    in PAI  usercommand  module  
    use loop endloop for internal table which store item level data 
    loop at item level data
    user command module 
    endloop.
    in module  driving program .
    module
    read table it_issue index tab_ctl-current_line transporting no fields.
      if sy-subrc = 0.
        it_issue-kostl = p_kostl.
        it_issue-ktext = p_ktext.
        it_issue-for_sys = p_for_sys.
        modify it_issue from it_issue index tab_ctl-current_line.
        clear it_issue.
      else.
        it_issue-kostl = p_kostl.
        it_issue-ktext = p_ktext.
        it_issue-for_sys = p_for_sys.
        append it_issue .
        clear it_issue.
      endif.
    endmodule  .
    regards
    deepak.

  • Mandatory field in sales order additional data tab

    Hi,
    I have added an extra field in additional data tab of sales order. 
    How can i make this field as mandatory for certain sales organisations ?
    TIA

    since it's conditional, I think I would add code in SAVE_DOCUMENT_PREPARE subroutine in MV45AFZZ, based on transaction code, prior values (YVBAP) and current values (XVBAP), and issue an error message, allowing user to return to the screens displaying Item table control, when the field is not properly populated.

  • Sales Order Additional Data

    Hi,
    I have 2 sales orders:
    SO1) with an entry in the Header Level field VBKA-KVGR1 (Additonal Data A).
    SO2) No entry in the Header Level field VBKA-KVGR1 (Additonal Data A).
    If I open SO1 in VA02 and F3 Back out of it without making a change, I am asked "do I want to Save Changes"?
    If I open SO2 in VA02 and F3 Back out of it without making a change, I am not asked the question.
    Anyone know why?
    Thanks.

    Hi Max,
    I said yes to the 'Save Changes' question but no new change document appeared.
    I'll do a debug now and see if there is a userexit somewhere changing something.
    From the quick debug that I have done, the Popup appears because...
    (SAPMV45B)R185D-DATALOSS = X here:
    SAPLV00F / LV00FF0D
    Form DIALOG_AUSGEBEN
    IF T185D-DIADYN NE SPACE.
      PERFORM DIALOGFELD_DYNAMISCH USING MODUL-POOL USER_DATALOSS
                                         USER_FIELD.
      ASSIGN (USER_FIELD) TO <FS1>.
    Datenverlust -
      CHECK <FS1> NE SPACE. -
    >>>>> 'X'
    ENDIF.
    (USER_FIELD)  = (SAPMV45B)R185D-DATALOSS
    In the other one (SAPMV45B)R185D-DATALOSS = '  '
    Thanks.

  • Sales Order Addl data B field changes

    Dear friends,
    I have a requirment here to record document changes for a customized field Zlabdip in sales order additional data B.
    The document changes automatically gets recorded for standard SAP fields, how i can add document changes for a Z field.
    Kindly suggest.
    Regards,
    Praveen Lobo

    Hi Praveen,
    Goto dataelemnt of the zfield and in tab' further characteristics' Check the option 'change document'.
    Reddy

  • Adding new fields to additional data B screen in sales transaction

    Hi All,
    I have a requirement like this I need to add 3 input fields and 1 push button(select oppurtunity) in additional data B screen of sales order transaction.If I click on this button I want geneate one pop up dialog box just like as search help box and I should be able to search data for these 3 fields data based on some 4 input fields data?How can I acheive this?I can add button and what I have to write the code in PBO and PAI of this screen?Please some body help me in this regard.
    Regards
    Mahesh

    Hi friend,
    In SAP we can add few fields from maintain reserve fields. Please go through it;
    Maintain Reserve Fields In Customer Master
    There are reserve fields in the customer master record which are not used in the standard system. They are available for use and are as follows:
    Customer group 1 (View: V_TVV1 Field:KVGR1)
    Customer group 2 (View: V_TVV2 Field:KVGR2)
    Customer group 3 (View: V_TVV3 Field:KVGR3)
    Customer group 4 (View: V_TVV4 Field:KVGR4)
    Customer group 5 (View: V_TVV5 Field:KVGR5)
    You can find the fields in the customer master record under the sales and distribution data in Sales. Choose additional data under Environment.
    It is advisable to change the field description (Data elements KVGR1 to KVGR5).
    This is described in the system modifications in the Reserve fields unit of the customer master record:
    Reserve Fields in Customer Master
    Record
    In this step you maintain the valid entries for the individual views.

  • 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 make Sales Order Delivery Date show 30days after Posting Date

    I have problem programming the SBO 2005A- Sales Order Delivery Date automatically add 30 days based on Posting Date, in VB.Net.
    Has someone tried it before ?

    Sorry i did not describe clearly.
    I was developing vb.net with SAPBuiCom (UI API).
    When Sales Order screen and the Delivery Date was empty. In my program i need to auto insert the Delivery Date field with 30days after the Posting Date.
    And when user change the posting date, the delivery date will auto refresh.
    KC

  • Sales orders flow - dates difference

    Dear All,
    I need to build a model for a report which needs to have the days difference between the sales order creation date, delivery date, goods issue date  and billing date. The lowest level of detail should be the Sales Order/Item and one Sales Order/Item can origin different Delivery Items.
    Base on this, i'm wondering how can i model this scenario...
    Do you have any suggestion?
    Thanks in advance and best regards,
    Nuno

    Hi,
    I need to build a model for a report which needs to have the days difference between the
    Sales order creation date,
    Delivery date,
    Goods issue date ,
    Billing date.
    In your question you didn't mension what differences you need
    Eg:
    Sales order creation date - Delivery date
    Goods issue date - Billing date
    Sales order creation date - Billing date
    Delivery date - Goods issue date
    Like what combination you need?.
    Steps:
    Bring all InfoObejcts into Cube and once youn have all required InfoObecjts in your cube then in reporting level you can play like any thing. So first bring all Dates data into Cube. Use 0SD_C03 InfoCube with relavent datasources.
    Then Use Formula Variables with Replacement pathes and then do simple Substractions at reporting level. Your problem is resolved.
    See the below Article how I'm calculating Age of teh Material. Here I'm using Custome Exit Variable to get teh System Data, but in your case you don't need it, you just use Formula Variable with Replcemet Path and replace with Date and then do Substartion.
    Calculating the Ageing of the Materials
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/a-c/calculating%20the%20ageing%20of%20the%20materials.pdf
    https://wiki.sdn.sap.com/wiki/display/profile/Surendra+Reddy
    Thanks
    Reddy

  • Sales order item data & sales order schedule data

    Hello,
    I have a Sales Orders cube which is pulling data from two DSOs (one for sales order item data and the other for sales order schedule data). The common fields between these two DSOs is the Sales Order number but in my cube I have dual entries for each Sales Order document (item and schedule info).
    Example of how the data looks now:
    Sales Order . . Item Cat. . . Article . . . Net Price . . . Delivery . . . Act GI Date
    1. . . . . . . . . ...TAN. . . . . ABC123. . . .10
    1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 . . . . . . . . 01/01/2000
    2. . . . . . . . . ...TAN. . . . . CBA321. . . .15
    2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 . . . . . . . . 01/02/2000
    How do I merge the data on the Sales Order number in the cube so it looks like below?
    Sales Order . . Item Cat. . . Article . . . Net Price . . . Delivery . . . Act GI Date
    1. . . . . . . . . ...TAN. . . . . ABC123. . . .10 . . . . . . . . . .1 . . . . . . . . 01/01/2000
    2. . . . . . . . . ...TAN. . . . . CBA321. . . .15 . . . . . . . . . .2 . . . . . . . . 01/02/2000
    Many thanks,
    Matt

    > Hello,
    >
    > I have a Sales Orders cube which is pulling data from
    > two DSOs (one for sales order item data and the other
    > for sales order schedule data). The common fields
    > between these two DSOs is the Sales Order number but
    > in my cube I have dual entries for each Sales Order
    > document (item and schedule info).
    >
    Two previous remarks:
    1) If you need to report on very detailed data consider doing an info-set joining both datastores. 2 reasons why:
    - not a good idea to report on very detailed information (sales order, GI dates) on cube level, if you have a scenario with lots of data. You end up with big dimension tables a poor report times;
    - there are better alternatives, like drill-through from cube query to DS query with report to report interface or Datastore-based reporting...so...
    With this solution you do not need to change the data model, I think, but test to be sure. See if the reporting times are acceptable. If not...
    2) First confirm your requirements, because what you show in your example as "to-be" have details that do not make sense, probably..
    - if you have more that one schedule line for each item then you would have many times the item information like material/price;
    - if not or if you could cope with that, then you can consider:
    2.1) create a new DS that agregattes from the previous on, with the same key of sales order item; do you have schedule line kf's? if so you these KF's should be additive in DS update; But if you may have more one scheduled line for 1 item then you have to decide what to do with the GI data (keep the last one posted, use code..) and other characteristics.
    2.2) update the shedule line datasource to the sales order item DS; same comments apply.
    2.3) maintain the missing data in the cube update rules from sheduled lines DS. Using code, refer to the respective item in the order item ODS. You would have to make sure that DS's data are correctly activated before updating the infocube.
    What solutions to choose?
    2.1 is better in terms of flexibility and architecture...because you could re-arrange the new DS to answer future needs, without loosing the 1st line DS's data;
    2.2 choose if data volumes and disk space are a concern...
    or
    2.3 it's OK, but i do not like it because of what explained in point 1...
    Message was edited by:
            Miguel Costa

  • Sales Order Item Data & Sales Order Schedule Lines

    Hello,
    I have a Sales Orders cube which is pulling data from two DSOs (one for sales order item data and the other for sales order schedule data). The common fields between these two DSOs is the Sales Order number but in my cube I have dual entries for each Sales Order document (item and schedule info).
    Example of how the data looks now:
    <b>Sales Order . . Item Cat. . . Article . . . Net Price . . . Delivery . . .  Act GI Date</b>
    1. . . . . . . . . ...TAN. . . . . ABC123. . . .10  
    1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 . . . . . . . . 01/01/2000
    2. . . . . . . . . ...TAN. . . . . CBA321. . . .15  
    2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 . . . . . . . . 01/02/2000
    How do I merge the data on the Sales Order number in the cube so it looks like below?
    <b>Sales Order . . Item Cat. . . Article . . . Net Price . . . Delivery . . .  Act GI Date</b>
    1. . . . . . . . . ...TAN. . . . . ABC123. . . .10 . . . . . . . . . .1 . . . . . . . . 01/01/2000 
    2. . . . . . . . . ...TAN. . . . . CBA321. . . .15 . . . . . . . . . .2 . . . . . . . . 01/02/2000  
    Many thanks,
    Matt

    Hi Matt,
        Its no possible If you are maintaining data at Order Level.
    Try to introduce one more ODS/DSO in between ODS's and CUBE by keeping Sales Order only key field. Load data from both DSO's in required fields only. Then PUSH delta to CUBE. In this why you can maintain 1 record. Try to compress cube(with delete Zero Record Rows) to delete unnessasary records.
    Hope it Helps
    Srini

  • 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

  • Sales order proposal dates

    Hi Gurus,
    Sales order dates proposals are showing tommorrows even though i have given 10 days in house production time and first date in the sales order line item showing todays date.
    So could you tell me where exactly these dates are driving from? Any configuration is required meet the dates?.
    Thanks in advance.
    Quantum.

    Hi,
    In sale order general screen the date which is shown against the line item will be the delivery date which will be defualt the based on the configuration in Tcode : VOV8.
    Goto Tcode : VOV8 and select the document type of the sales order and dgoto detailed screen where you can find the Header : Request deleivery date / pricing date/purchase order date, Under that there will be a check box fot Proposed Delivery Date. If that check box is ticked system will by default the current date as Delivery date against the Item in Sales Order.
    If you want the system to consider the lead time i.e Inhouse production days mentioned in Material Master, select the item in the sales order and do the avaialbility check in the sales order for the item.
    regards
    radhak mk

  • Is there any bapi that i can create sales order and date

    Hi Gurus
    is there any bapi that i can create sales order and date .

    This appears to be related to Problem With BAPI_SALESORDER_CREATEFROMDATA but without the detail. If you want to ask again, please add that detail.
    locked
    Rob

  • Sales Order Posting Date on Invoice PLD

    Hello,
       I am trying to post a Sales Order Posting Date to our Invoice PLD.  It is not native information to the Invoice PLD so I will probably need to create a query which I can then place into a UDF on the Invoice.
    Any out there have a solution?
    Thanks.
    Edited by: Arellano Mario on Jul 8, 2009 1:16 AM

    Hi
    Sorry , for keeping messing up :
    38.45.0 is referring to Invoice row level base key
    logic is saying  Delivery number is equal to invoice row level base key
    If you look at the link and Gagan answer ,your problem should have been solved .
    Please close this thread if your problem is solved .
    Thann you
    Bishal
    Definitely need a coffee to start my day
    Edited by: BIshal Adhikari on Jul 9, 2009 6:44 AM
    Edited by: BIshal Adhikari on Jul 9, 2009 6:44 AM

Maybe you are looking for