Sales Order is not creating with reference to Quantity Contract.

Dear SAP Experts,
I am creating a Sales Order with reference to quantity contract but system showing an error *"""Material SUG10051 does not exist in RG1 Table for Excise Group 42 - Message no. ZCOMM002"""* i am not getting y system showing this error because all the necessary configuration for series group is maintained already.
Please advise me what should i do.
Looking forward for your quick response on the same.
Regards
Parul Deshwal

Hi
As per STD SAP, all billing items will be updated in RG1 register.
The control is in J1ID where you have to select "Material and Chapter ID combination" and choose the tab "Material type".
There against the billing material code, maintain "F"
Also check setting
IMG --> Logistics General --> Taxes on Goods movements --> India Check Basic Settings, Master Data, A/c deteremination, Business transactions and Tools.

Similar Messages

Want to see the sales order which is created with reference

Hi Gurus,
I created a sales order with reference to a contract. I forgot the sales order number and contract number..
how can i search my sales order which is created w.f.t acontract.we dont have the access for VA42, VA45.
cHEERS,
Sumith

Dear Sumith
Go to VA05, click your mouse on "Further sel.criteria", so that you will have some options to choose like "Sales Document Type", "Created by".
You can choose either of these and execute so that it will display the respective document.
thanks
G. Lakshmipathi

Error : Sales order 'create with Reference' to the contract

We have made a value contract. Now we are trying to make a Sales order 'create with Reference' to the contract.
when we do that, we am getting error 'copying material in any value contract item is not permitted'
Any help or directions would be greatly appreciated . We are on Ecc 6.0
Rohit

As of now my value contract has just one material. so i dont need assortment module settings. right?
in VTAA settings are as follows
Target type: OR
Source type: ZK1
there is only on item category
Target item category: TAN
Source item category: WKN
Copying requirement : 301
update doc flow : 2
pricing type : C
cont item copy mode : A
DataT am using 151,102,002
There are no schedule line.
Rohit
Edited by: rohit kumar on May 15, 2008 7:36 PM

Sales order should not copy the net value from contract

Hi,
When we are creating the sales order,Where we can maintain that sales order should not copy the net value from contract.
Regards
Prabudh

Hi,
When I am creating the sales order with reference to contract,it's copying the net value and quantity from the contract.
But I want that sales order should not copy the net value and quantity from the contract and user can take new required quantity at the time creating the sales order.
Regards
Prabudh

Sales order do not create after SAP upgradation to package EHP7

Dear Experts,
SAP client is recently upgraded to EHP7. Since then we are observing difficulty in Sales order creation [VA01] manually [with or without order reference].
When click on SAVE button, entire screen display get freezed, without any message [Error/Information/Warning] pop-up. it seems as if system was trying to display message; caused due to any kind of event occurrence; but unable to show up.
Moreover, when we click on "BACK" or "EXIT" button, then it prompts choices to save the data. Yet again we receive the same freeze response whenever chose "Yes" option.
Please note:- before up-gradation, we were able to create orders with the same data, what we are using to create now.
Any help or clue on this subject would be highly appreciated.
Thank you for all your help.
Best regards,
Rahul Agarwal

Hi,
did you check what are the sales orders Enhancements that are activated with EHP7 under T.code-SFW5

Debit Memo Request not created with reference to CRM Confirmation

Hi,
I have confirgured the service order and confirmation as a follow up document,
Service order contains both service line item and sales item,
Service order is replicated to ERP as sales order with sales item,
how ever debot memo request is not getting created in ERP against the confirmation i have created ,
*     i can see the price flowing to KO03 at CO, also have made settings in SCRM Billing integration for debit memo ,a new debit memo order type is created with internal number range.
*     my employee also exists in ERP,
*     item category for confirmation is also set to external billing when conpleted.
*     i am able to complete the confirmation document without any errors.
followed c26 documents.
please Suggest
regards
Nikhil Chugh

Hello Nikhil
Did you map your CRM transaction types with ERP Transaction as per step
3.2.4.4 of c26.
Regards
Naresh

Sales Order should not generated if total value of contract is released

Dear All,
We are creating sales order wrt to Value Contract, but it shows the warning message if value exceed above the contract value.
We required if contract value exceed then sales order should not be generated.
Thanks & Regards,
PM

Hi
Check in VOV7 for item category WKN under tab value contract Contract release control select B Error msg if trt value exceeded...
Reg
JJ

How to block the sales order for not creating requirement

Dear All,
My client want that whenever a sales order is raise, that should not go create requirement for production unless until account department check whether the prices etc are correctly put or not
how can i do this
thanks

I suggest you can try to use the functionality of Status Profile.
Create one Status Profile with 2 line items-
1: First line : Pricing Approval or PR and check what all you want to block if this status is assigned to the order type.
2: Second line : Released and check what all you want to be released once the Approval is done.
So by default the status profile - Pricing Approval will be assigned to the Sales Order during order creation. Then after your accounts department check the pricing and approves , they can change the status to Released and the order can be processed further.
Regards
Sai

My sales order is not created and showing erroe

dear sir,
i ve already created the customer with internal no
and wen i m raising the sales order one erroe is comming" no costomer master record exist for the sold to party" error no 199
but the customer master is still there and i ve also created the custome in same sales area wer i m raising the sales order
before some dayz i ve done a blonder that i ve deleted the partner functions from strandard but again i ve created as standard .then i used it for my account group.
so why the error is comming please help
its really urgent....
with regards
subrat

Subrat,
since you deleted the cusomer master and since your number assignment is internal , once you delete the customer master you would not be able to create the customer master with same OLD Number range , it will take a new number this time for the sold to party which is created.....
and that is why the old one will not work , use the customer master and it should work fine ...
Cheers

Document is not creating with reference to existing doc?

Hello
I am trying to COPY the MS Word(document 'as is' including formatting options) of my_existing_word_doc into a new_word_doc, both documents path is local machine, so, i wrote the code as below,
REPORT ZWORD_TEST.
INCLUDE ole2incl.
DATA: w_word            TYPE ole2_object,
      w_document        TYPE ole2_object,
      w_selection       TYPE ole2_object,
      w_find            TYPE ole2_object,
      w_replacement     TYPE ole2_object,
      w_font            TYPE ole2_object,
      w_paragraphformat TYPE ole2_object,
      w_line(80).
START-OF-SELECTION.
* Create OLE automation object of type Word.Application.
CREATE OBJECT w_word 'Word.Application'.
* Display MS-Word when executing the program.
SET PROPERTY OF w_word 'Visible' = 1.
* Open doc
CALL METHOD OF w_word 'Documents' = w_document.
CALL METHOD OF w_document 'Open' EXPORTING #1 = 'C:\Users\MIKE1\Downloads\Desktop\my_existing_word_doc.docx'.
* Add data to the new MS-Word document.
CALL METHOD OF w_word 'Selection' = w_selection.
* CALL METHOD OF w_selection 'ParagraphFormat' = w_paragraphformat.
* CALL METHOD OF w_selection 'Font' = w_font.
*Select All
CALL METHOD OF w_selection 'WholeStory'.
*Copy
CALL METHOD OF w_selection 'Copy'.
*Close Doc
CALL METHOD OF w_document 'Close'.
FREE OBJECT w_document.
FREE OBJECT w_selection.
* FREE OBJECT w_paragraphformat.
* FREE OBJECT w_font.
*Open new blank doc
CALL METHOD OF w_word 'Documents' = w_document.
CALL METHOD of w_document 'Add'.
* Add data to the new MS-Word document.
CALL METHOD OF w_word 'Selection' = w_selection.
* CALL METHOD OF w_selection 'ParagraphFormat' = w_paragraphformat.
* CALL METHOD OF w_selection 'Font' = w_font.
CALL METHOD of w_selection 'Find' = w_find.
*Paste from Clipboard
CALL METHOD of w_selection 'PasteAndFormat'
    EXPORTING #1 = 1.
*Find and Replace
CALL METHOD of w_find 'ClearFormatting'.
CALL METHOD OF w_find 'Execute' EXPORTING
    #01 = 'Old_text'
    #10 = 'Revised_Text'
    #11 = 1.
FREE OBJECT w_document.
FREE OBJECT w_word.
but,
1) Its not creating any new document at all!
2) When should i pass my new document name as "my_new_word_doc", and where should i mention the saving location/path for this new doc?
3) Even i am not sure that, its copying the doc as whole? bcz i can check becausem, its niot creating a new doc!
Thank you

Hi
As per STD SAP, all billing items will be updated in RG1 register.
The control is in J1ID where you have to select "Material and Chapter ID combination" and choose the tab "Material type".
There against the billing material code, maintain "F"
Also check setting
IMG --> Logistics General --> Taxes on Goods movements --> India Check Basic Settings, Master Data, A/c deteremination, Business transactions and Tools.

Error while posting a sales order created with reference from contract for

Hi,
I am posting a sales document( Type: WA) created with reference from contract document( type wk2) for delivery. The item category in the sales order of the Item is WAN. On posting this document for delivery I am getting the error as "Item category WAN is not defined". Please help me out how to resolve this issue.
Thanks
Jayant

Hi Jayant,
I think its value contract releated error,
You suppose to check material item category group through T.code-MM02 into sales2 tab and maintain VCIT,
and do item category assignment through T.code- VOV4.
plz.maintain like that,
WK2 -          -VCIT-         -           - WAN(contract item category),
wk2 -          -        -VCTR-          - WAN((contract item category),
you should also maintain same against your standard Sales Document type and for Standard Item category into VOV4,
WA(standard docu.type) -VCIT-                             -                -TAN(your standard docu.type item category),
WA(standard docu.type) -         -VCTR(item usage)-              -TAN(your standard docu.type item category),

BAPI Sales order create with reference

Hi
I need to use BAPI to create sales order with reference to Quantity Contract. The line item material quantity would be less than or equal to quantity contract quantity.
Sales order needs to be created with new quantity.
Quantity contract quantity change needs to be maintained.
Document flow needs to be maintained.
Is any one aware if this is possible using BAPI_SALESORDER_CREATEFROMDAT2. If yes, how?
Any insights would be highly appreciated.

Hi Maninder,
The BAPI does not allow the Pricing Conditions to be sourced from the Contract. I debugged the BAPI and it uses a piece of code (don't recall which subroutine though) from SAPMV45A which is relevant for dialog processing where it reads from the VBAP and *VBAP structures. Well this structure is only populated when you are using the Front End transaction (VA41, VA42, etc). Because this structure is empty, pricing conditions do not flow across.
Here is a little prototype program I whipped up to test my method of creating a Sales order and then changing the Sales Order:
REPORT ypat_salesorder_create LINE-SIZE 256.
* This program will create a ZOC Sales Order with Reference to Contract
* 20000720 / 10. This will be done via BAPI. There are 2 BAPi calls,
* BAPI_SALESORDER_CREATEFROMDAT2 and BAPI_SALESORDER_CHANGE. We need to
* perform 2 BAPI calls as the BAPI to create the Sales Order does not
* bring across the Pricing Conditions properly. To get around this we
* create the Order with reference to the Contract, then we get the
* related Pricing Conditions from the COntract and then update the newly
* created Order.
* Constants
CONSTANTS: c_contract LIKE vbak-vbeln VALUE '0020000720',
           c_item      LIKE vbap-posnr VALUE '000010'.
* Structures
* Structure to hold BAPI Header
DATA: st_bapisdhd1   LIKE bapisdhd1.
* Internal Tables
* Sales Order Create BAPI Return Messages
DATA: tbl_return     TYPE STANDARD TABLE OF bapiret2
                     WITH HEADER LINE.
* Sales Order BAPI Line Item
DATA: tbl_bapisditm TYPE STANDARD TABLE OF bapisditm
                     WITH HEADER LINE.
* Sales Order BAPI Line Item
DATA: tbl_bapisditmx TYPE STANDARD TABLE OF bapisditmx
                     WITH HEADER LINE.
* Sales Order BAPI Pricing Conditions
DATA: tbl_bapicond   TYPE STANDARD TABLE OF bapicond
                     WITH HEADER LINE.
* Sales Order BAPI Partner Functions
DATA: tbl_bapiparnr TYPE STANDARD TABLE OF bapiparnr
                     WITH HEADER LINE.
* Sales Order BAPI Schedule Lines
DATA: tbl_bapischdl TYPE STANDARD TABLE OF bapischdl
                     WITH HEADER LINE.
* Sales Order BAPI Schedule Lines
DATA: tbl_bapischdlx TYPE STANDARD TABLE OF bapischdlx
                     WITH HEADER LINE.
* Sales Order BAPI Pricing Conditions
DATA: tbl_bapicondx    TYPE STANDARD TABLE OF bapicondx
                       WITH HEADER LINE.
* Customer Enhancement for VBAK, VBAP, VBEP
DATA: tbl_bapiparex    TYPE STANDARD TABLE OF bapiparex
                       WITH HEADER LINE.
* Table to hold BAPI Detail Conditions
DATA: tbl_bapisdcond   TYPE STANDARD TABLE OF bapisdcond
                       WITH HEADER LINE.
* Table to hold Return Messages from Sales Order Change BAPI
DATA: tbl_return_chg TYPE STANDARD TABLE OF bapiret2
                      WITH HEADER LINE.
* Variables
DATA: g_vbeln_created   LIKE vbak-vbeln,
      g_valid_contract TYPE c,
      g_cont_price_date TYPE d.
* Start of Selection
START-OF-SELECTION.
PERFORM validate_contract.
PERFORM create_sales_ord.
PERFORM update_sales_ord.
* End of Selection
END-OF-SELECTION.
PERFORM write_output_report.
* Subroutines
*&      Form create_sales_ord
*       Create the Sales Order
FORM create_sales_ord .
PERFORM populate_bapi_tables.
PERFORM call_create_sales_ord_bapi.
ENDFORM.                    " create_sales_ord
*&      Form populate_bapi_tables
*       Fill up the BAPI Tables
FORM populate_bapi_tables .
PERFORM populate_bapi_header.
PERFORM build_bapi_partners.
PERFORM build_bapi_items.
PERFORM build_bapi_sched_lines.
ENDFORM.                    " populate_bapi_tables
*&      Form populate_bapi_header
*       Build BAPI Header Details
FORM populate_bapi_header .
CLEAR st_bapisdhd1.
st_bapisdhd1-doc_type     = 'ZOC'.         "Order type
st_bapisdhd1-sales_org    = '026'.         "Sales Org
st_bapisdhd1-distr_chan   = '00'.          "Dist Channel
st_bapisdhd1-division     = '00'.          "Division
st_bapisdhd1-purch_no_c   = 'Cust Po No'. "Cust PO No
st_bapisdhd1-name         = 'Orderer'.     "Name of Orderer
st_bapisdhd1-ord_reason   = ''.            "Order Reason
st_bapisdhd1-sales_off    = '3001'.        "Sales Office
st_bapisdhd1-sales_grp    = '301'.         "Market Area
IF g_valid_contract = 'X'.
    st_bapisdhd1-price_date = g_cont_price_date.
ENDIF.
ENDFORM.                    " populate_bapi_header
*&      Form build_bapi_partners
*       Build BAPI Partner Functions
FORM build_bapi_partners .
CLEAR tbl_bapiparnr.
tbl_bapiparnr-partn_role   = 'AG'.
tbl_bapiparnr-partn_numb   = '0000100750'.
APPEND tbl_bapiparnr.
CLEAR tbl_bapiparnr.
tbl_bapiparnr-partn_role   = 'WE'.
tbl_bapiparnr-partn_numb   = '0000504472'.
APPEND tbl_bapiparnr.
ENDFORM.                    " build_bapi_partners
*&      Form build_bapi_items
*       Build The BAPI Line Items
FORM build_bapi_items .
DATA: l_matnr LIKE mara-matnr.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      input = '10000072'
    IMPORTING
      output = l_matnr.
CLEAR tbl_bapisditm.
tbl_bapisditm-itm_number = c_item.
IF g_valid_contract = 'X'.
    tbl_bapisditm-ref_doc     = c_contract.
    tbl_bapisditm-ref_doc_it = c_item.
    tbl_bapisditm-ref_doc_ca = 'G'.       "Contract
ENDIF.
tbl_bapisditm-material    = l_matnr.
tbl_bapisditm-plant       = '3012'.
tbl_bapisditm-target_qty = '5.000'.
tbl_bapisditm-target_qu   = 'M3'.
tbl_bapisditm-item_categ = 'ZZOC'.
tbl_bapisditm-sales_dist = '301'.
tbl_bapisditm-dlv_prio    = '02'.
tbl_bapisditm-prc_group5 = '080'.
tbl_bapisditm-cust_mat35 = 'kdmat'.
tbl_bapisditm-route       = 'TESYS'.
tbl_bapisditm-usage_ind   = 'CIV'.
APPEND tbl_bapisditm.
CLEAR tbl_bapisditmx.
tbl_bapisditmx-itm_number = c_item.
tbl_bapisditmx-ref_doc    = 'X'.
tbl_bapisditmx-ref_doc_it = 'X'.
tbl_bapisditmx-ref_doc_ca = 'X'.
tbl_bapisditmx-material   = 'X'.
tbl_bapisditmx-updateflag = 'I'.
tbl_bapisditmx-plant      = 'X'.
tbl_bapisditmx-target_qty = 'X'.
tbl_bapisditmx-target_qu = 'X'.
tbl_bapisditmx-item_categ = 'X'.
tbl_bapisditmx-sales_dist = 'X'.
tbl_bapisditmx-dlv_prio   = 'X'.
tbl_bapisditmx-prc_group5 = 'X'.
tbl_bapisditmx-cust_mat35 = 'X'.
tbl_bapisditmx-usage_ind = 'X'.
tbl_bapisditmx-route      = 'X'.
APPEND tbl_bapisditmx.
ENDFORM.                    " build_bapi_items
*&      Form build_bapi_sched_lines
*       Build the BAPI Schedule Lines
FORM build_bapi_sched_lines .
CLEAR tbl_bapischdl.
tbl_bapischdl-itm_number = c_item.
tbl_bapischdl-req_qty     = '1'.
tbl_bapischdl-req_date    = sy-datum.
APPEND tbl_bapischdl.
ENDFORM.                    " build_bapi_sched_lines
*&      Form build_bapi_conditions
*       Pull the BAPI Pricing Conditions from the Contract
FORM build_bapi_conditions .
LOOP AT tbl_bapisdcond.
    CLEAR tbl_bapicond.
    MOVE-CORRESPONDING tbl_bapisdcond TO tbl_bapicond.
    APPEND tbl_bapicond.
    CLEAR tbl_bapicondx.
    tbl_bapicondx-itm_number = tbl_bapicond-itm_number.
    tbl_bapicondx-cond_st_no = tbl_bapicond-cond_st_no.
    tbl_bapicondx-cond_count = tbl_bapicond-cond_count.
    tbl_bapicondx-cond_type = tbl_bapicond-cond_type.
    tbl_bapicondx-updateflag = 'I'.
    tbl_bapicondx-cond_value = 'X'.
    tbl_bapicondx-currency   = 'X'.
    tbl_bapicondx-cond_unit = 'X'.
    tbl_bapicondx-cond_p_unt = 'X'.
    tbl_bapicondx-varcond    = tbl_bapicond-varcond.
    APPEND tbl_bapicondx.
ENDLOOP.
ENDFORM.                    " build_bapi_conditions
*&      Form call_create_sales_ord_bapi
*       Call the Sales Order Create BAPI
FORM call_create_sales_ord_bapi .
CLEAR g_vbeln_created.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
    EXPORTING
      order_header_in    = st_bapisdhd1
    IMPORTING
      salesdocument      = g_vbeln_created
    TABLES
      return             = tbl_return
      order_items_in     = tbl_bapisditm
      order_items_inx    = tbl_bapisditmx
      order_partners     = tbl_bapiparnr
      order_schedules_in = tbl_bapischdl.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = 'X'.
ENDFORM.                    " call_create_sales_ord_bapi
*&      Form update_sales_ord
*       Update the newly created Sales Order with the Pricing Conditions
*       from the Contract
FORM update_sales_ord .
CHECK g_valid_contract EQ 'X'.
PERFORM get_contract_details.
PERFORM build_bapi_conditions.
PERFORM call_change_sales_ord_bapi.
ENDFORM.                    " update_sales_ord
*&      Form get_contract_details
*       Get Contract Details
FORM get_contract_details .
* Need to manually get the relevant Pricing Conditions as the BAPI
* BAPISDORDER_GETDETAILEDLIST causes problems when we call the BAPI
* BAPI_SALESORDER_CREATEFROMDAT2 and BAPI_SALESORDER_CHANGE (I think
* this is due to the fact that these BAPIs belong to the same Function
* Group and there must be some common structures that are not cleared
* causing us all sorts of grief when we try and call the next BAPI)
DATA: tbl_konv TYPE STANDARD TABLE OF konv WITH HEADER LINE.
DATA: tbl_komv TYPE STANDARD TABLE OF komv WITH HEADER LINE.
DATA: tbl_vbak TYPE STANDARD TABLE OF vbak WITH HEADER LINE.
* Pricing Condition Master
DATA: BEGIN OF tbl_t685a OCCURS 0,
          kschl     LIKE t685a-kschl,
          kaend_wrt LIKE t685a-kaend_wrt,
        END OF tbl_t685a.
SELECT *
         INTO TABLE tbl_vbak
         FROM vbak
         WHERE vbeln = c_contract.
READ TABLE tbl_vbak INDEX 1.
SELECT *
         INTO TABLE tbl_konv
         FROM konv
         WHERE knumv = tbl_vbak-knumv AND
               kposn = c_item.
CHECK sy-subrc EQ 0.
* We now need to make sure we only bring across the Condition Types that
* are EDITABLE. If we bring across non editable conditions (such as
* 'ZPR1') the Change Sales Order BAPI will fail
SELECT kschl kaend_wrt
         INTO TABLE tbl_t685a
         FROM t685a
         FOR ALL ENTRIES IN tbl_konv
         WHERE kappl     EQ 'V'             AND "Sales
               kschl     EQ tbl_konv-kschl AND
               kaend_wrt EQ 'X'             AND "Value is Editable
               kmanu     NE 'D'.                 "Process manually
* Prepare for Binary Search
SORT tbl_t685a BY kschl.
LOOP AT tbl_konv.
    READ TABLE tbl_t685a WITH KEY kschl = tbl_konv-kschl BINARY SEARCH.
    IF sy-subrc EQ 0.
      MOVE-CORRESPONDING tbl_konv TO tbl_komv.
      APPEND tbl_komv.
    ENDIF.
ENDLOOP.
CHECK NOT tbl_komv[] IS INITIAL.
* Map KOMV into the more BAPI friendly BAPISDCOND structure
CALL FUNCTION 'MAP_INT_TO_EXT_STRUCTURE'
    TABLES
      fxvbak        = tbl_vbak
      fxkomv        = tbl_komv
      fxbapikomv    = tbl_bapisdcond
    EXCEPTIONS
      entry_missing = 1
      OTHERS        = 2.
ENDFORM.                    " get_contract_details
*&      Form call_change_sales_ord_bapi
*       Call the Change Sales Order BAPI
FORM call_change_sales_ord_bapi .
DATA: st_head_chg      LIKE bapisdh1x,
        st_logic_switch TYPE bapisdls.
CHECK NOT g_vbeln_created IS INITIAL.
CHECK g_valid_contract EQ 'X'.
st_head_chg-updateflag     = 'U'.
st_logic_switch-cond_handl = 'X'.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
    EXPORTING
      salesdocument    = g_vbeln_created
      order_header_inx = st_head_chg
      logic_switch     = st_logic_switch
    TABLES
      return           = tbl_return_chg
      conditions_in    = tbl_bapicond
      conditions_inx   = tbl_bapicondx.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = 'X'.
ENDFORM.                    " call_change_sales_ord_bapi
*&      Form write_output_report
*       Produce Output Report
FORM write_output_report .
IF NOT g_vbeln_created IS INITIAL.
    WRITE:/ 'Success! Sales Order', g_vbeln_created, 'was created!'.
ELSE.
    WRITE:/ 'Failure! Sales Order was not created!'.
ENDIF.
SKIP.
WRITE:/ 'Sales Order Create Log'.
LOOP AT tbl_return.
    WRITE:/ tbl_return-type, tbl_return-id, tbl_return-number,
            tbl_return-message.
ENDLOOP.
SKIP.
WRITE:/ 'Sales Order Change Log'.
LOOP AT tbl_return_chg.
    WRITE:/ tbl_return_chg-type, tbl_return_chg-id,
            tbl_return_chg-number, tbl_return_chg-message.
ENDLOOP.
ENDFORM.                    " write_output_report
*&      Form validate_contract
*       Make sure that the Contract is Valid
FORM validate_contract .
DATA: l_gueen LIKE vbak-gueen,
        l_prsdt LIKE vbkd-prsdt.
SELECT SINGLE vbak~gueen vbkd~prsdt
         INTO (l_gueen, l_prsdt)
         FROM vbak
         INNER JOIN vbkd
         ON vbak~vbeln = vbkd~vbeln
         WHERE vbak~vbeln = c_contract AND
               vbkd~posnr = '000000'.
IF sy-datum LE l_gueen.
* Contract is valid! Set Order Price Date
    g_valid_contract = 'X'.
    g_cont_price_date = l_prsdt.
ENDIF.
ENDFORM.                    " validate_contract
Hope this helps.
Cheers,
Pat.

Sales Order CReated with Reference

Hi,
I created a sales order with reference to an existing order. I created delivery based on the new order that was created with reference. HOwever, if i try to get the sales order number of my delivery, the sales order that i am getting is the sales order number that was referenced. How will I retreived the new sales order number from VBFA?
Thanks,
Louisse

Hello,
         We can follow the below Procedure to get the Sales Order Number from VBFA Table.
1. Input the Delivery in VBELN field to get VBELV (Sales Order)
    Number with VBTYP_V = 'C' (Order).
2. Now, if the Sales Order which is fetched is the one which is
    referenced, then Input the Sales Order Number again in the
    VBFA Table into the Field VBELV and fetch the Sales Order
    Number (New) in the VBELN Field with VBTYP_N = 'C'.
3. You should be able to satisfy your requirement.
Hope it was clear.
Thanks and Regards,
Venkat Phani Prasad Konduri

How to differentiate the Purch Orders created with reference to in table

Hi all
how to differentiate the Purch Orders which are created with reference to Purch requsitions, contract, manual by copying inforecord in the table EKKO/EKPO? Is there any Field Indicators?
Rgds
Ramesh

Hi Ramesh,
Go through EKPO there is a Table BANFN it will update when you create a PO with reference to PR
Do se11 > Table EKPO> CtrlShiftF10 > Assign any of PO no. in the EBELN > Execute > you will find BANFN table
it indicates Purchase Requisition Number. it will update when you create PO with reference to PR.
Regards,
Vraj

Create with reference - Screen settings

Hi,
Please help me find where we do settings for the create with reference screen. When we try to create a sales order in VA01 and click create with reference it gives a small pop up on which there are tabs (Order, Inquiry, Quote, etc..). I want to know where we are the settings for this small pop up (create with reference ) screen.
I remember we can change the default tab (ex: Quotes to Order) on the create with reference screen. I am unable to find it now.
Thanks !!

Hello,
I've just face the same question and found that its possible to use a couple of user setting parameters :
VRA parameter to set a doc number eg.. 0
VRV parameter to set the default reference type (A-> Inquiry, B->Quotation, C-> Order, G-> Contract)
This is working only for sales order type.
Christophe.

Sales Order is not creating with reference to Quantity Contract.

Similar Messages

Maybe you are looking for