BW - Change Sales Order name

All,
I am trying to rename some of the sales order types descriptions. Is this something i can do in Info Objects? The reports shows the name of the sales order type and its description. I need to change the description and cant figure out how i can change that in RSA1. Any help is appreciated!
thanks

Hi,
I think you are pointing to sales document type and the relevant infoobject for this is 0DOC_TYPE..
You want to change the description of some of the documnet type then go to RSA1--Infoobjectsearch the relevant infoobject for which you want to change the descriptionRT clickMaintain master dataexecuteselect the document which you need to edit-hit the edit buttonchange the description---save.
Hope it helps.
Regards,
AL
Edited by: AL1112 on Dec 16, 2011 7:27 AM

Similar Messages

Error received while changing sales order.

Hi All,
while changing sales order we have received error message "An internal program error has occured.See note 44283".
So could you plesae explain me what needs to be done.
Thanks in advance.

To avoid to store inconsistent data in the future, activate the following method of the BADI                           BADI_SD_SALES:
> 1 - Transaction SE18
> 2 - Definition name: BADI_SD_SALES Menu: Implementation -> Overview double-click on implementation: IM_CORE_CHECK
> 3 - Now you will get an overview on the methods and you see also that the implementation IM_CORE_CHECK is inactive
> 4 - Press the change button and activate
This check works in the following way:
> 1 - if the number of items is less than 10 and there is an inconsistency the system will not store the data and an A-message will occur.
> 2 - If the number of items is greater than 10 and less than 50 and there is an inconsistency the data will be stored and an I-message will occur.
> 3 - if the number of items is greater than 50 there is no check because performance.
Edited by: Gerard Magorrian on Aug 6, 2010 4:01 PM

How to change pricing Conditions in Sales order in change sales order bapi

Hi Experts,
How to change pricing Conditions in Sales order in change sales order bapi.
I have used the 2 function modules bapi-changesalesorder and sd salesdocument change, But it is creating the new record , instead of changing the existing one, Could please assist regarding the same
Thanks in Advance .
NLN

HI NLN
I have just tried on my system and managed to overwrite the existing price by passing the following parameters.
Import Paramters:
 SALESDOCUMENT - Sales Document Number
 ORDER_HEADER_INX - UPDATEFLAG as 'U'.
 LOGIC_SWITCH - Import Structure - Pass 'X' to LOGIC_SWITCH-COND_HANDL.
Tables:
 CONDITIONS_IN - ITM_NUMBER,
 COND_COUNT, -> Condition counter same as KONV-ZAEHK generally it is '01'
 COND_TYPE,
 COND_VALUE,
 CURRENCY.
 CONDITIONS_INX - ITM_NUMBER,
 COND_COUNT,
 COND_TYPE,
 UPDATEFLAG as 'U',
 CURRENCY.
 Hope i have clarified your query.
Kind Regards
Eswar

End User Transaction for Mass Change Sales Orders

Hello,
Transaction MASS can be used to change sales orders using object type BUS2032, however, end users are not allowed access to MASS.
In most other cases, the object types can be accessed by individual transactions, for example, MEMASSPO for BUS2012 and XD99 for KNA1.
But I cannot seem to find a similar transaction for object type BUS2032, does anyone know whether one exists or how to create such a shortcut.
Thanks,
Jake.

Hi
See SAP Note 483303 - BUS2032: Only sales orders of category VBAK-VBTYP = 'C'
Regards
Eduardo

Getting error in while changing sales order which is created using BAPI

Hi All,
   I have created the sales order using BAPI ( BAPI_SALESORDER_CREATEFROMDAT1 ) and i am successfully creating sales order using this BAPI. But while i want to change sales order iam changing Shipping Conditions in Header Data of sales order .its giving an error .can any know any thing about this.
Error mesage :    No status object is available for SDI 300082407/10    (Order Number/Item Number)
In Header i am passing these values ...
     wa_order_header_in-doc_type = vbak-auart.
    wa_order_header_in-sales_org = vbak-vkorg.
    wa_order_header_in-distr_chan = vbak-vtweg.
    wa_order_header_in-division = vbak-spart.
Do i required to pass the below values ? in Header structure ( BAPISDHEAD1 ).
REFOBJECTTYPE
REFOBJECTKEY
REFDOCTYPE
Regards,
Sudhakar Reddy A

rectified

Changing Sales Order PARTNER from 'MASS' transaction

Hi,
I have a requirement to change partner details (e.g. SHIP TO party from SH1 to SH2) for sales order. I need to use tcode 'MASS' (Mass maintainance) for BUS2032. But it does not have the option to change partner details.
Can anybody let me any approach to achieve this. If we can do it through a config or may be creating a custom business object etc...
I could found out the thread below talking about the same issue, but there is no solution to that. I want to build the solution around SAP standard and not interested for BDC/LSMW/CATT etc.
Mass changes Sales order partners
Thanks,
Madhu
Edited by: Madhu K on Nov 1, 2011 11:58 PM

Alan
I am ok to create a custom tcode for MASS. Do I need to copy the BUS2032 or the whole TCODE?
My major concern is, how to get the VBPA structure to the selection screen so that it ll show me the I/P fields to enter Old Ship to and New ship to..
Can You please give me some idea on this.
Thanks
Madhu

New sales order and Change sales order in item level or delete at item leve

I got one requirement. Daily i have to display one report on new sales orders created on that day and any sales order item is modified or any item is deleted or any item is added.
                  How to get the sales order numbers and position numbers which will follow above creteria. I found one function module but it is not giving position numbers and new sales order details.
         Is there any BAPI for this requirement.

I am using "CHANGEDOCUMENT_READ" function module to get the new sales orders created and changed sales order items on a particular time. This function module is getting data from CDHDR and CDPOS tables. But only change sales orders is coming. New sales orders which is created on that time is not getting.
          One of my friend is telling like we have to activate one change pointer to retrive new sales orders also. Which is like there will be one check box.
Is any body having idea on this. Please reply me on briefly with the code to retrive new sales orders and changed sales orders

BAPI / FM to change Sales order item data

Hi,
I need a BAPI or FM to update the following fields of VBAP (Sales Document Item Data)
KZWI2 - Subtotal 2 from pricing procedure for condition
KZWI3 - Subtotal 3 from pricing procedure for condition
KZWI4 - Subtotal 4 from pricing procedure for condition
KZWI5 - Subtotal 5 from pricing procedure for condition
I found FM: ISM_SALES_ITEM_CHANGE for this, but when I use it, it gives me dump for some data object 'XJKNBK'.
Does any one have idea on how to use this FM or if any other FM is there please let me know?
Thanks & Regards,
Sunanda.

hi Sunanda..
I think you can try the Bapi 'BAPI_SALESORDER_CHANGE'. You can make use of its Tables Parameter CONDITIONS_IN and CONDITIONS_INX.
example:
How to change pricing Conditions in Sales order in change sales order bapi
thanks,
Padma

Change Sales Order, Delivery, Billings Reports

Hi Gurus,
Can any body please tell me is there any Report for change logs of Change Sales Order, Delivery,
Billings & Change report of Customer & Material,
Regards,
Sai

Hi,
There are no standard reports to display the changes made in the Sales orders and the details you had asked.
But for the latest changes you can check in the Table :Header details for change CDHDR and for Item details CDPOS
Or Based on your requirement you can go for a Customized Report
rgds
psk

Error in change sales order.

Hi ,
my process is : First create SO than Billing than Delivery. i need to change the sales order Batch when
delivery saved.
When i change Sales order Batch withouting creating billing it is changing Fine through BAPI FM .
But when i create So --Billing --- delivery than in this case Sales order batch not changing.
it is giving error like below.
Field CHARGE Can not be changed VBAPKOM 000010 is ready for input'
Message is comming from message class V1 and Message no 739.
PLease Reply .
If any clue Have.
Thanks.

Hi,
When you create a Billing Document for the Sales Order it is no longer possible to change a lot of fields (as these fields have been copied to the Billing Document). Field Batch is one of those fields.
So if you have to include the batch in the Sales order you must update this field prior to creating the Billing Document.
Regards,
John.

Change Sales Order material characteristics

Dear Pals,
I have a question for changing Sales Order material characteristics by item.
If i want to change the sales order's item conditions, I can modify the internal table "XKOMV" in user exit "USEREXIT_SAVE_DOCUMENT_PREPARE"
Is there any internal table for Sales Order's characteristics can i use   in user exit "USEREXIT_SAVE_DOCUMENT_PREPARE" ?
Or any FM or BAPIs can get the internal table for characteristics and characteristics value for Sales Order item?
Thank you!

You can use BAPI_SALESORDER_CHANGE.
1. Get the SO detail using BAPISDORDER_GETDETAILEDLIST.
2. MODIFY the ORDER_CFGS_* internal tables and update.
        CALL FUNCTION 'BAPISDORDER_GETDETAILEDLIST'
          TABLES
            order_cfgs_value   = gt_char
            order_cfgs_ref       = gt_char_ref
            order_cfgs_inst      = gt_char_ins.
        MODIFY gt_cfgs_*.
        CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
         TABLES
            order_cfgs_value   = gt_char
            order_cfgs_ref       = gt_char_ref
            order_cfgs_inst      = gt_char_ins.
Refer SAP note 549563.

Change Sales Order Contract Data FM

Hi Friends
Kindly let me know if there is any function module or BAPI to change Sales order Contract Data of each line item. 'BAPI_SALESORDER_CHANGE' dosent have that.
Thanks

Hi Ram,
Check will this helps you ...
call function 'BAPI_CUSTOMERCONTRACT_CHANGE'
exporting
SALESDOCUMENT = vbeln
CONTRACT_HEADER_IN = w_header
CONTRACT_HEADER_INX = w_headerin
INT_NUMBER_ASSIGNMENT = 'X'
ORDER_HEADER_INX
BEHAVE_WHEN_ERROR = 'P'
LOGIC_SWITCH
TESTRUN = 'X'
convert = 'X'
importing
salesdocument = v_order
salesdocument = vbeln
tables
return = t_return
CONTRACT_items_in = t_items
CONTRACT_ITEMS_INX = r_items
CONTRACT_partners = t_partners
CONTRACT_schedules_in = t_sched
CONTRACT_conditions_in = t_conds
CONTRACT_text = t_texts .
Regards,
Poornima

Problem in updating Billing plan while changing Sales order

Hi All,
 I am using the BAPI 'BAPI_SALESORDER_CHANGE' to change a Prepaid Sale order.After calling this BAPI ,I am calling the function module 'BILLING_SCHEDULE_SAVE' to update the Billing plan of the changed Sale order(Billing plan dates for Billing type ZF1 are changed).
 The updated date values are getting reflected in the screen when I view through the transaction VA02 and the values are also updated in FPLT table but the values are not getting reflected in the table VKDFS.
 Since the values are not getting reflectedin the table VKDFS the billing date is not correct while we view in the transaction VF04.
 Please provide your valuable suggestions for updating the Billing date in VKDFS table.
 Thanks in advance for your help.
Thanks and regards,
Siva

Hi,
I had the same problem. Here is an example code to resolve it:
REPORT ytestfg.
DATA: i_bsid LIKE bsid OCCURS 0,
 i_bsid2 LIKE bsid OCCURS 0.
TABLES: bsid.
DATA: doc LIKE vbak-vbeln,
 pos(6) TYPE n.
DATA e_fpla LIKE fpla.
DATA e_fplt LIKE fpltvb OCCURS 0 .
DATA: zfpla LIKE fplavb OCCURS 0,
zfplt LIKE fpltvb OCCURS 0.
DATA zfplt2 LIKE fpltvb OCCURS 0 WITH HEADER LINE.
doc = 'G03060619'.
pos = '000010'.
CALL FUNCTION 'SD_SALES_DOCUMENT_READ'
EXPORTING
 document_number = doc.
CALL FUNCTION 'SD_SALES_BILLINGPLAN_READ'
EXPORTING
 i_vbeln = doc
 i_posnr = pos
IMPORTING
 e_fpla = e_fpla
TABLES
 e_fplt = e_fplt
EXCEPTIONS
 no_billingplan_allowed = 1
 no_billingplan_found = 2
 OTHERS = 3.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Read the billing plan
CALL FUNCTION 'BILLING_SCHEDULE_READ'
EXPORTING
 fplnr = e_fpla-fplnr
I_VFKDAT =
I_BFKDAT =
TABLES
 zfpla = zfpla
 zfplt = zfplt
Upddate the ZFPLT2 table with the new values
MOVE zfplt[] TO zfplt2[].
READ TABLE zfplt2 INDEX 1.
zfplt2-afdat = '20080927'.
Very important to set field updkz = 'U' ***
zfplt2-updkz = 'U'. "--> UPDATE!!
MODIFY zfplt2 INDEX 1.
CALL FUNCTION 'BILLING_SCHEDULE_SAVE'
TABLES
 fpla_new = zfpla
 fpla_old = zfpla
 fplt_new = zfplt2 " --> NEW
 fplt_old = zfplt.
CALL FUNCTION 'SD_SALES_DOCUMENT_SAVE'.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
Regards,
Edited by: PHO_BA on Mar 9, 2009 5:28 PM

Change sales order - for reasons of cost management item cannot be deleted

Hello Friends,
When I try to delete a line item from sales order below error is fired and it doesnot allows to delete the items which has a WBS element.
The function name is :BAPI_SALESORDER_CHANGE
The error message is as below:
    ORDER_HEADER_IN has been processed successfully
    For reasons of cost management, item 001001 cannot be deleted
    Error in ITEM_IN 001001
    KONVKOM has been processed successfully
    KONVKOM has been processed successfully
    KONVKOM has been processed successfully
    KONVKOM has been processed successfully
    KONVKOM has been processed successfully
    The sales document is not yet complete: Edit data
    Sales document 0002012766 was not changed
Information
    Sales order: 0002012766
    Item       : 001001
    WBS element: 2012766-001 The wbs status is "REL"
I found a similar problem on the forum but not really a solution other than giving a suggestion as "Enter a reason for rejection at item level.".
but when I put the field ORDER_ITEM_IN-REASON_REJ = 'Z1' and ORDER_ITEM_INX-REASON_REJ = 'X',the error is still occurring.
'Z1'-WBS has been cancelled
How can I remove this item from the sales order?
Please help me.....
Best Regards,
bluebaby

Hello Lakshmipathi,
thank you very much for answering my question..
But how I get the file SAP note 14097,I was search this file in SDN and google but cannot find this file,if you know pls give me a hyperlink to view the content,thanks a lot.
Best regards,
Sophia

User exit for changing Sales order lines.

Hello experts ,
I want to delete the field "ROUTE" from all of the orders lines in sales orders, I have been using "USEREXIT_SAVE_DOCUMENT_PREPARE" but it does not seems to do the job.
What is the name of user exit that i have to use for this task and which structure should be used, is it xvbap ? is it vbap ?
Thanks for the help.
Avi.

Hi,
find the user exit u required.
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
Best regards,
venkatawamy.y

BW - Change Sales Order name

Similar Messages

Maybe you are looking for