Vertex help needed on sales order

so, this is the scenario i have:
i have 2 customers, A and B. A is exempt from tax, B is not. I have 2 materials in the line item: x and y. everything works fine with the customers and taxes. but when i go in for one of the line item materials (lets say x) and i change the tax classification to something that i have entered into vertex, where the customer should be taxed, and choose a customer that is exempt from tax, it shows no tax, when the material is suppose to have tax because of the tax classification. any suggestions on what i'm doing wrong?? ty!

Hi,
Maintain the condition record as per the combination you need to maintain the tax.
Regards,
Sp.Balaji.

Similar Messages

Help needed in sales order/ quality management

In standard sap it is possible to assign an inspection to the delivery type. But client wants a non standard sap inspection to be done at time of order. is it possible? If it is please do help me in customizing this. Thank you in advance.
M. Ali

hi,
Please try table VBFA with fields VBELV = <sales order> and VBTYP_N = 'J' (Shipping/Delivery).
and also try this also
if you know delivery number for order ,then you could use FM VTTP_READ
if you need delivery number from sales order then use VBAP-VGBEL
pass delivery number to FM or pass the value to VTTP Table
thanks,
<b><REMOVED BY MODERATOR></b>
Message was edited by:
Alvaro Tejada Galindo

Query help needed for Sales order panel user field query.

I have a user defined form field on sales order row level called = U_DEPFEEAMT
1, I would like this field to get the value from a field on this sales order row level multiplied by what is in point 2 below. The details of field in point 1 is :
Form=139, item=38, pane=1, column=10002117, and row=1
2. The contents in field 1 should be multiplied by a value coming from another user field linked to OITM master item.
The details of user field attached to OITM is :
OITM.U_DepositFeeON
Appreciate your help.
Thank you.

Try this one:
SELECT T0.U_DepositFeeON*$[$38.10002117.number\]
FROM dbo.OITM T0
WHERE T0.ItemCode = $[$38.1.0\]
Thanks,
Gordon

I need help on Complete Sales Order Cycle using Business One

Hai,
Actually I am crating an external application using Business one DI API, Now I need a Complete Cycle of Sales Order Cycle from Sales Order Creation to Goods issues, goods receipt ,invoice generation , pick and pack etc
Anybody Please help me out on generating a Complete Sales Order Cycle using Business One GUI or theory by using Business One
Please help me out in this regard
with regards
Somaraju

Somaraju,
You may want to look at the Sample Code example that is part of the 2005A Business One SDK that shows and external Business One interface written in VB.Net that shows how to create a Sales Order/Invoice in SAP Business One. This example can be found at: Start > Programs > SAP Business One > SDK > Samples > COM DI > 05. OrderAndInvoice. For complete training on the processes you are asking about from within the SAP Business One product, you can reveiw the SAP Business One eLearning product training if you are and SAP Business One partner in the areas that you have outlined at service.sap.com/smb.
Hope that helps,
Eddy

Help is needed in Sales order User Exits

Hi
Please Can anybody show the solution to my problem.
My problem is:
Using Table having 2 columns(Customer,Route), we have to display Route(present under shipping tab in Sales Order) in Sales Order. Route has to be displayed based on the customer present in the table.

hi,
Please try table VBFA with fields VBELV = <sales order> and VBTYP_N = 'J' (Shipping/Delivery).
and also try this also
if you know delivery number for order ,then you could use FM VTTP_READ
if you need delivery number from sales order then use VBAP-VGBEL
pass delivery number to FM or pass the value to VTTP Table
thanks,
<b><REMOVED BY MODERATOR></b>
Message was edited by:
Alvaro Tejada Galindo

Help with SE37 code needed - create sales order

Hi Guurus,
Can you please help? I finally finished with function creation (I just adopted the function, which I found in the system and it works ok, YEAH!!!)
BUT!!! It is working just for the sales order creation with one item.
Is it a big deal if you adopt my code that the function will have possibility to add more then one item?
Thanks in advance
Sao
Here is the code:
*FUNCTION Z_RFC_SD_SIMO_SALES_ORDER2.
*""Local interface:
**" IMPORTING
**"     VALUE(P_AUART) TYPE AUART DEFAULT 'zhp'
**"     VALUE(P_VKORG) TYPE VKORG DEFAULT 0001
**"     VALUE(P_VTWEG) TYPE VTWEG DEFAULT 07
**"     VALUE(P_SPART) TYPE SPART DEFAULT 01
**"     VALUE(P_AUGRU) TYPE AUGRU DEFAULT 001
**"     VALUE(P_BSTKD) TYPE BSTKD DEFAULT 'test si order avtom'
**"     VALUE(P_SOLD) TYPE KUNNR DEFAULT 21000069
**"     VALUE(P_SHIP) TYPE KUNNR DEFAULT 21000069
**"     VALUE(P_MATNR) TYPE MATNR DEFAULT 'SIOBRACUN'
**"     VALUE(P_MENGE) TYPE KWMENG DEFAULT 1
**"     VALUE(P_PLANT) TYPE WERKS_D DEFAULT 0001
**"     VALUE(P_ITCAT) TYPE PSTYV DEFAULT 'ZG2W'
**"     VALUE(P_LGORT) TYPE LGORT_D DEFAULT 0001
**" EXPORTING
**"     VALUE(V_VBELN) TYPE VBELN
**"     VALUE(RESULT) TYPE CHAR01
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.
HEADER DATA
*header-doc_type = p_auart.
*headerx-doc_type = 'X'.
*header-sales_org = p_vkorg.
*headerx-sales_org = 'X'.
*header-distr_chan = p_vtweg.
*headerx-distr_chan = 'X'.
*header-division = p_spart.
*headerx-division = 'X'.
**order reason
*header-ord_reason = p_augru.
*headerx-ord_reason = 'X'.
**PO number from MAX
*header-PURCH_NO_C = p_BSTKD.
*headerx-PURCH_NO_C = 'X'.
*headerx-updateflag = 'I'.
PARTNER DATA
*partner-partn_role = 'AG'.
*partner-partn_numb = p_sold.
*APPEND partner.
*partner-partn_role = 'WE'.
*partner-partn_numb = p_ship.
*APPEND partner.
ITEM DATA
*itemx-updateflag = 'I'.
*item-itm_number = '000010'.
*itemx-itm_number = 'X'.
*item-material = p_matnr.
*itemx-material = 'X'.
*item-plant = p_plant.
*itemx-plant = 'X'.
*item-target_qty = p_menge.
*itemx-target_qty = 'X'.
*item-target_qu = ' '.
*itemx-target_qu = 'X'.
*item-item_categ = p_itcat.
*itemx-item_categ = 'X'.
**item-STORE_LOC = p_LGORT.
**itemx-STORE_LOC = '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
*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.
*result = 'E'.
*ELSE.
*COMMIT WORK AND WAIT.
*result = 'S'.
*ENDIF.
*ENDFUNCTION.
Edited by: Saso Poljansek on Jan 22, 2008 10:23 AM

Hi,,
    Include           YCL_CREATE_SALES_DOCU                         *
     Form salesdocu
     This Subroutine is used to create Sales Order
     -->P_HEADER           Document Header Data
     -->P_HEADERX          Checkbox for Header Data
     -->P_ITEM             Item Data
     -->P_ITEMX            Item Data Checkboxes
     -->P_LT_SCHEDULES_IN Schedule Line Data
     -->P_LT_SCHEDULES_INX Checkbox Schedule Line Data
     -->P_PARTNER text    Document Partner
     <--P_w_vbeln text    Sales Document Number
DATA:
lfs_return like line of t_return.
FORM create_sales_document changing P_HEADER like fs_header
                                   P_HEADERX like fs_headerx
                                   Pt_ITEM   like t_item[]
                                   Pt_ITEMX like t_itemx[]
                                   P_LT_SCHEDULES_IN like t_schedules_in[]
                                   P_LT_SCHEDULES_INX like t_schedules_inx[]
                                   Pt_PARTNER like t_partner[]
                                   P_w_vbeln like w_vbeln.
This Perform is used to fill required data for Sales order creation
perform sales_fill_data changing p_header
                                   p_headerx
                                   pt_item
                                   pt_itemx
                                   p_lt_schedules_in
                                   p_lt_schedules_inx
                                   pt_partner.
Function Module to Create Sales and Distribution Document
perform sales_order_creation using p_header
                                     p_headerx
                                     pt_item
                                     pt_itemx
                                     p_lt_schedules_in
                                     p_lt_schedules_inx
                                     pt_partner.
perform return_check using p_w_vbeln .
ENDFORM.                                 " salesdocu
    Form commit_work
    To execute external commit                                    *
FORM commit_work .
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
   WAIT          = c_x
ENDFORM.                                 " Commit_work
Include ycl_sales_order_header          " To Fill Header data and Item data
Include ycl_sales_order_header.
     Form return_check
    To validate the sales order creation
FORM return_check using pr_vbeln type vbeln.
if pr_vbeln is initial.
    LOOP AT t_return into lfs_return .
      WRITE / lfs_return-message.
      clear lfs_return.
    ENDLOOP.                             " Loop at return
else.
    perform commit_work.                 " External Commit
    Refresh t_return.
    fs_disp-text = text-003.
    fs_disp-number = pr_vbeln.
    append fs_disp to it_disp.
if p_del eq c_x or p_torder eq c_x or
    p_pgi eq c_x or p_bill eq c_x.
    perform delivery_creation.           " Delivery order creation
    endif.                               " If p_del eq 'X'......
endif.                                 " If p_w_vbeln is initial
ENDFORM.                                 " Return_check
*&      Form sales_order_creation
      text
     -->P_P_HEADER text
     -->P_P_HEADERX text
     -->P_PT_ITEM text
     -->P_PT_ITEMX text
     -->P_P_LT_SCHEDULES_IN text
     -->P_P_LT_SCHEDULES_INX text
     -->P_PT_PARTNER text
FORM sales_order_creation USING    P_P_HEADER like fs_header
                                    P_P_HEADERX like fs_headerx
                                    P_PT_ITEM like t_item[]
                                    P_PT_ITEMX like t_itemx[]
                                    P_P_LT_SCHEDULES_IN like t_schedules_in[]
                                    P_P_LT_SCHEDULES_INX like t_schedules_inx[]
                                    P_PT_PARTNER like t_partner[].
    CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
    EXPORTING
      sales_header_in     = p_p_header
      sales_header_inx    = p_p_headerx
    IMPORTING
      salesdocument_ex    = w_vbeln
    TABLES
      return              = t_return
      sales_items_in      = p_pt_item
      sales_items_inx     = p_pt_itemx
      sales_schedules_in = p_p_lt_schedules_in
      sales_schedules_inx = p_p_lt_schedules_inx
      sales_partners      = p_pt_partner.
ENDFORM.                    " sales_order_creation
this is code to create sales document
plzz reward if it is usefull...
plzz dont forget to reward......

Name of the structure needed for sales order user exit

Hi,
I am planning to write a user exit which will insert the data into my ztable the moment the new sales order is created and is saved.
I have identified FORM USEREXIT_SAVE_DOCUMENT as the necessary user exit. But the problem is that while inserting the data into the ztable I cannot insert the data from vbak as the data will be inserted into this table after the SO is saved.
Thus I need to identify a structure which is used to populate the vbak table so that it simultaneously inserts the data in the ztable as well. Can anyone help me with the name of the structure so that these fields i.e. vbeln, vkorg, vtweg, spart are inserted into my ztable?
Also need to know how to convert the net value i.e. vbak-netwr in Indian Rupees as it gets stored as Dollars ....
Thanks,
Vinod.

Hi,
One of the structure being used is RV45A, there are several other str's being used as well for various calculations,
check out program SAPMV45A for the same.
& in order to convert vbak-netwr to rupees use the below statemetnt,
WRITE vbak-netwr TO zvbak-netwr CURRENCY INR.
Regards,
Raghavendra
Message was edited by:
raghavendra ay

Help me on sales order history,

hi all,
i need to develop a report on sales order history,
please help me, what are the related tables to get sales order history

the SAPGUII cannot help you on this.
you should refer to the ERP-SD forum at SAP ERP Sales and Distribution (SAP SD)

Need All Sales Order user exit

Neeed all Sales Order user exits

Hi,
Check these Exits and their corresponding Programs
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET
In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Reward points if helpful.
Regards
Ravi

Duplicate purchase oredr number message need in sale order creation

Hi,
My requirement is for a user exit for sales order creation.
When user create a sales order and put customer purchase order number based on purchase order number
user entered it will check data base table and if its duplicate entry then throw the error.
So, Requirement is :
1: Give error for duplicate purchase order number.
I need user exit name.
Please help.
Regards,
Moderator Message: Please search before posting basic questions. Thread locked.
Edited by: Neil Gardiner on Apr 29, 2011 9:31 AM

Whether to allow duplicate PO numbers from a customer is a configuration setting.... However, what you're asking seems strange.... what has company code got to do with it, unless you want to allow PO numbers to dupllicate across SAP company codes...e.g., customer orders on PO #1 from company code 001 and PO #1 from company code 002....
Usually, we would want to apply duplicate PO code checking at the customer number level, wouldn't we? If customer 1 sends me PO #1 and customer 100 sends me PO #1, I certainly would want to accept both orders.
Consult your SD functional specialist about configuring this option.

Free Goods Problem and User Exit if needed in Sales Order

Hello All,
The problem is related to Free Goods in Sales Order which is given with an example -
We have maintained Free Goods ( T Code - VBN1) in inclusive scenario which is as follows -
For 210 PAC (Pack) of Material A 18 PAC Free.
Where 1 PAC = 20 BT (Bottle) and 20 PAC = 1 CV (Case Pack)
In the material master of Material A the Base Unit Of Measurement (UOM) = PAC and Sales UOM = Blank so that we can use any conversion factor maintained for the material.
The conversion factors maintained for Material A are as follows -
1 BT = 1BT
1 PAC = 20 BT
1 CV = 20 PAC
Now when we are raising sales order for 11 CV the free goods are not generated in the Sale Order.
Again if we maintain the Sales UOM in CV and raise the sales order it is showing :
10 CV as main item and 1 CV as Free which is wrong because in the conversion factor we have already maintained 1CV = 20 PAC , Whereas in the inclusive scenario it is given 11CV = 210 PAC and 210 PAC = 18 PAC is free.So in any case it is taking into account 2 more PACs.
Please suggest what need to be done in this case in respect of User Exit or Source Code in ABAP if needed.
Thanks & Regards
Priyanka Mitra

Hello Priyanka Mitra,
We are facing a problem same as you.
How did you solve this problem?
We are very glad if you teach it concretely.
Please advise your solution to us.
Thanks.

Sales order with MRP run but no need of sales order stock while PGI

Dear Gurus,
We have scenario in company that we want to run MRP for sales order & generate requirements. But while doing post goods issue for same sales order, sales order stock need not be present.
Please tell which planning strategy, strategy group or else should be used here.
Thanks in Advance !!
Thanks,
Vishwas

Hi,
Please configure in the following manner..
create a strategy group say Z9..in this maintain main strategy as 20 and alternate strategy as 10... Now assign this strategy group to material in material master in MRP3 View..
Now create sales order say A and run MRP with MD50..after completion of production you will get Sales order stock.. now convert this sales order stock unrestricted use stock..
Now before you are doing PGI for sales order A... go to sales order change VA02 and change the requirement type to KSL from KE and then system will all you to do PGI with unrestricted use stock...
Thanks
Kumar

Help with deleted sales orders

Hi everyone,
I have an issue with sales order deletion. We load BW nightly. If a sales order is created one day and deleted the next day we get a record for a positive qty and a record for a negative qty, this is ok. The problem is when the record is created and deleted the same day, this creates a negative qty amount that does not have a positive amount to cancel out and in turn throws our sales qty's off. Can anyone help?
Thank you,
Aaron Blasi

Hi AVR,
Thanks for the reply. What I am trying to figure out is why the extractor sends only the negative amount record when the sales order is created and deleted the same day. What happened to the positive amount record? does anyone know why or has anyone come accross this issue.
Thanks,
Aaron

Help on Indent Sales Order Creation - Missing Items in Purchase Requisition

Hi Experts,
We have Indent Sales setup where when we create Indent Sales Orders it will also create Purchase Requisitions. But we have encountered a lot of of missing items in the Purchase Requisition that are in Indent Sales. Have you encountered this kind of behavior? What are the usual suspects (configuration-wise) for this scenario?
Thanks for your Help!

hi,
please check the SCHEDULE LINES for those PR is getting generated and also for not generating.
PLEASE CHECK THE SCHEDULE LINE CATEGORY CONTROL FEATURES on the same
hope this clears your issue
balajia

Help! losing sales orders in the order list from cumulative value VK13

Hi Experts,
Now we are facing a problem that when user going to check for which orders the condition record was used, the T-Code is VK13.
Path: VK13 -> Display the condition record -> additional data -> Extra -> Cumulative values -> First Sales orders
they found some orders are missing in that list, but in previous system, the list was included all the order numbers which used this condition record, so it's confusing for them to tracking the utility of this condition record.
Can anyone share your idea on it such as 1. whether user exit exists there, what the user exit name? 2. whether configuration should be changed, which configuration should be modified, your idea will be highly appreciated!

Sorry for confusing, the thing is only the first 3 orders of individual month will be displayed. No issue now

Vertex help needed on sales order

Similar Messages

Maybe you are looking for