Change sales order user status

Hello experts,
I'm trying to update the user status with the following code without success:
DATA : LIT_STATUS_COMT       TYPE CRMT_STATUS_COMT,
       WA_STATUS_COMT        LIKE LINE OF LIT_STATUS_COMT,
       LIT_FIELD_NAMES       TYPE CRMT_INPUT_FIELD_NAMES_TAB,
       WA_INPUT_FIELD_NAMES LIKE LINE OF LIT_FIELD_NAMES.
SELECTION-SCREEN BEGIN OF BLOCK AAA.
PARAMETERS: P_GUID TYPE CRMT_STATUS_COM-REF_GUID,
            P_STAT TYPE   CRMT_STATUS_COM-STATUS.
SELECTION-SCREEN END OF BLOCK AAA.
CLEAR WA_STATUS_COMT.
WA_STATUS_COMT-REF_GUID       = P_GUID.
WA_STATUS_COMT-REF_KIND       = 'A' .
WA_STATUS_COMT-STATUS         = P_STAT. " Pass the user status
WA_STATUS_COMT-USER_STAT_PROC = 'ZOR00001'. " Value for the User Status Profile.
WA_STATUS_COMT-ACTIVATE       = 'X'.
INSERT WA_STATUS_COMT INTO TABLE LIT_STATUS_COMT.
WA_INPUT_FIELD_NAMES-FIELDNAME = 'ACTIVATE'.
APPEND WA_INPUT_FIELD_NAMES TO LIT_FIELD_NAMES.
CALL FUNCTION 'CRM_STATUS_MAINTAIN_OW'
    EXPORTING
      IT_STATUS_COM        = LIT_STATUS_COMT
    CHANGING
      CT_INPUT_FIELD_NAMES = LIT_FIELD_NAMES
    EXCEPTIONS
      NOT_ALLOWED          = 1
      ERROR_OCCURRED       = 2
      WARNING_OCCURRED     = 3
      OTHERS               = 4.
DATA: LT_OBJECTS_TO_SAVE TYPE CRMT_OBJECT_GUID_TAB,
        LS_OBJECTS_TO_SAVE LIKE LINE OF LT_OBJECTS_TO_SAVE.
LS_OBJECTS_TO_SAVE = P_GUID.
APPEND LS_OBJECTS_TO_SAVE TO LT_OBJECTS_TO_SAVE.
CALL FUNCTION 'CRM_STATUS_SAVE_OW'
   EXPORTING
     IT_HEADER_GUID           = LT_OBJECTS_TO_SAVE
best regards,
Ronen.

R.R,
I already tried that without success:
INCLUDE CRM_STATUS_CON.
INCLUDE CRM_LOG_STATES_CON.
SELECTION-SCREEN BEGIN OF BLOCK AAA.
PARAMETERS: P_OBJNR TYPE CRM_JSTO-OBJNR,
              P_STAT TYPE   CRM_JEST-STAT.
SELECTION-SCREEN END OF BLOCK AAA.
START-OF-SELECTION.
CALL FUNCTION 'CRM_STATUS_CHANGE_EXTERN_OW'
EXPORTING
*   CHECK_ONLY                = ' '
    OBJNR                     = P_OBJNR
    USER_STATUS               = P_STAT
*   SET_INACT                 = ' '
*   IV_REF_KIND               =
*   IV_OBJECT_TYPE            =
*   IV_NO_1O_MAINTAIN         =
* IMPORTING
*   STONR                     =
* EXCEPTIONS
*   OBJECT_NOT_FOUND          = 1
*   STATUS_INCONSISTENT       = 2
*   STATUS_NOT_ALLOWED        = 3
*   OTHERS                    = 4
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
   WAIT          = 'X'
* IMPORTING
*   RETURN        =
any other suggestions?
Ronen.

Similar Messages

Creating check on officers who can change a sales order - User Status

The user needs to create a check on persons who can change (User Status) on the sales order created.
The sales order are created by a group of people. These group of people can not be allowed to change the sales order - User Status(In header Detail).
Only a second level user users should be allowed change this user status.
Can it be done at configuration level. Or should we use an Exit?
Thanks in advance.

Hi Sunoj,
I never have used this auth. objects, but if you want to set restrictions on some users, search before in auth. objects. As I told you, you can use the tcode SU24 for this purpose. Do the selection, see the result, try it with tcode PFCG and check it.
If you can do something with customizing tools or other standard tools (as authoritation tools) avoid the use of enhancements, BADI, BTE'S and so on. If you don't find the solution, then go to userexits.
I hope this helps you
Regards
Eduardo

Userexit for updating sales order user status based on PO

Hi.
My clients requirent is
Sales order user status should get updated based on production order creation,GR for PO creation etc.
Basically depending on PO & GR For PO,various user stauts in sales order should get updated.
Can you please suggest me some userexits in PP for this requirement?
I am a SD Consultant and not having much idaes about PP
Thanks
Nisha

hi,
if you are not going to update it in the SO..
then you need different exits as those are different transactions.

Userexit for updating sales order user status based on Production Order

Hi.
My clients requirent is
Sales order user status should get updated based on production order creation,GR for PO creation etc.
Basically depending on PO & GR For PO,various user stauts in sales order should get updated.
Can you please suggest me some userexits in PP for this requirement?
I am a SD Consultant and not having much idaes about PP
Thanks
Nisha

hi,
if you are not going to update it in the SO..
then you need different exits as those are different transactions.

Function module for changing Work order user status in IW32

Hi,
I want to change the work order user status in IW32 using ABAP.
Is there any function module to do so or any other way? I have tried using BDC but this does not work.
Please suggest.
Regards,
Naba
Edited by: n. saha on Nov 5, 2008 6:46 AM

I am getting Same Problem.
fi_methods-method = 'SAVE'.
APPEND fi_methods.
fi_methods-refnumber = 1.
fi_methods-objecttype = 'USERSTATUS'.
fi_methods-method = 'CHANGE'.
fi_methods-objectkey = '002000002453'.
APPEND fi_methods.
fi_userstatus-user_st_text = 'COMM'.
fi_userstatus-user_langu   = 'EN'.
fi_userstatus-CHANGE_EVENT = ' 01 '.
APPEND fi_userstatus.
CALL FUNCTION 'BAPI_ALM_ORDER_MAINTAIN'
TABLES
    it_methods    = fi_methods
    it_userstatus = fi_userstatus
    return        = fi_return.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
Above code I am using and there the message comes like
T ID                   NUM           MESSAGE
S IW                   080           Order saved with number 2000002453
S IWO_BAPI2     110           BAPI control was ended
can any on know what is wrong in this? please help if having knowledge.
Thank You,
Jahnavee Trivedi

Sales Order User Status

Hi,
is there any FM or user-exits to set the User Status of the Sales Order Line Item at the time of Order Creation.
( status profile is created with 3 status in BS02 and assigned to the order line item. user exit / fm has to change the status assigned to the order based on certain conditions )
Lot of FM are available to update the status after Order Creation. I'm lookin for one at the time of order creation where i could use in the exit MV45AFZZ.
looking for your inputs.
Thanks,
Arun

Thanks, I have gone through this. This needs a Object Number to update the status.
In my case i wont have the object number at the time of order creation.
Thats the problem.

BAPI for changing Work order user status in IW32

Hello Experts,
I am getting Same Problem in updating status via BAPI, BAPI_ALM_ORDER_MAINTAIN. Its not giving any error but even not update status.
I know i can use this for changing the user status also but not sure how to carry out things.
I used this code.
fi_methods-method = 'SAVE'.
APPEND fi_methods.
fi_methods-refnumber = 1.
fi_methods-objecttype = 'USERSTATUS'.
fi_methods-method = 'CHANGE'.
fi_methods-objectkey = '002000002453'.
APPEND fi_methods.
fi_userstatus-user_st_text = 'COMM'.
fi_userstatus-user_langu   = 'EN'.
fi_userstatus-change_event = ' 01 '.
APPEND fi_userstatus.
CALL FUNCTION 'BAPI_ALM_ORDER_MAINTAIN'
TABLES
    it_methods    = fi_methods
    it_userstatus = fi_userstatus
    return        = fi_return.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
Above code I am using and there the message comes like
T ID                   NUM           MESSAGE
S IW                   080           Order saved with number 2000002453
S IWO_BAPI2     110           BAPI control was ended
can any on know what is wrong in this? please help if having knowledge.
Thank You,
Jahnavee Trivedi

I am getting Same Problem.
fi_methods-method = 'SAVE'.
APPEND fi_methods.
fi_methods-refnumber = 1.
fi_methods-objecttype = 'USERSTATUS'.
fi_methods-method = 'CHANGE'.
fi_methods-objectkey = '002000002453'.
APPEND fi_methods.
fi_userstatus-user_st_text = 'COMM'.
fi_userstatus-user_langu   = 'EN'.
fi_userstatus-CHANGE_EVENT = ' 01 '.
APPEND fi_userstatus.
CALL FUNCTION 'BAPI_ALM_ORDER_MAINTAIN'
TABLES
    it_methods    = fi_methods
    it_userstatus = fi_userstatus
    return        = fi_return.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
Above code I am using and there the message comes like
T ID                   NUM           MESSAGE
S IW                   080           Order saved with number 2000002453
S IWO_BAPI2     110           BAPI control was ended
can any on know what is wrong in this? please help if having knowledge.
Thank You,
Jahnavee Trivedi

Sales order system status

Hi All,
we want to change the sales order system satus, then we found we can only do it in item level.since in one sales order we may have many items, if we change the system status by manually one item by one item, it cost time, I wonder in SAP 6.0 if we can do batch change sales order system status? If have, please tell me how to do it?
Regards,
Jagan

Hi Raj,
Thank you for the reply.The problem here is there are 100 line items in a sales order and user wants to change the item status (in the status tab in item level data) from A3-A4 ( example here is A0-SO created,A1-SO changed,A2-SO released,A3-PO created,A4-Delivery created,A5-SO closed) for all line items.In this Sales order 10 line items have not got the Goods receipt.But all other items have got.So he dont want to go to each and every line item to check and update the status of the GR,since it is time consuming process.So he is looking for the possibility in the header level like when he update the status in Heder level,it has to change the status in item level or if any item is not relevent for status change from A3-A4 (means the item present status is not in A3) it should throw a message.
Regards,
Jagan

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

Change Confirmed Qty in Sales Order User exit/ATP User exit

HI
We have a requirement to change the ATP Qty for certain meterials & Order Types duing sales Order User exit(FORM USEREXIT_MOVE_FIELD_TO_VBEP.? ) or ATP User exit.( ATP...OUT?).
Is this ok to update the XVBEP in FORM USEREXIT_MOVE_FIELD_TO_VBEP of MV45AFZZ ?
Our requirement will be like this, for one order type ZSAL( and for certain Materials) we need to reserve 4 qty, if any order comes with 10 qty and the confimed qty is only 6( total available stock at present) , then we should only confirm 2 qty for the other order type( For Non ZSAL Order Type), and reserve the 4 QTY for ZSAL Order Type.
If there are multiple schedule lines for an Item, we need to reduce the qty equally( as possible) from all schdule lines.
i.e. date1 qty 4
date2 qty 6,
in this case we should confirm Date1 QTY 2, date2 qty 4, so that the remaining 4 will be reserved for ZSAL Order type.
Whats the Best way to achieve this ?
Edited by: agrud agrud on Sep 8, 2011 4:01 AM

Hi Agrud,
Did you check the possibilities with configuration.If it is not possible with configuration then you can use that exit.Before i used this but only to display not to change any thing.
Regards,
Madhu.

How the sales order header status update?

Hello,
In the sales order header "STATUS" tab is there, under this status tab we can find OBJECT status if we click that object status it shows the Object number,Object category,status profile and status with status no. on which bases this status will update in the sales order header?
my case is Status "10-xxxx" set automatically for some orders.
Could you plz let me know on which bases, the status will be updated in the sales order?
Regards|KS

Hi
SAPu2019S GENERAL STATUS MANAGEMENT FUNCTIONALITY
General Status Management replaced order status management functionality in recent SAP releases (4.6C). This discussion will address general status management, as this is how SAP allows user statuses for controlling objects in this and future releases.
General Status Management applies to internal orders, project definitions, WBS elements, production orders and many other objects in SAP. For the purposes of this discussion we will concentrate on status management for internal orders and WBS elements. A list of all objects relevant for status management will be made available upon request.
A status is an indicator that fulfills two functions. First, it informs you that a particular status has been reached. For example, an internal order has been created and released; a settlement rule has been entered; a particular business transaction has been executed, etc. Second, it influences the business transactions you can perform for a particular status. A status can allow a business transaction; allow a business transaction but issue a warning message; or prohibit a business transaction altogether. If a warning message is issued it is up to the user whether the business transaction is carried out or not.
Statuses can be used to control and communicate. Statuses can be used in reporting (show me a report of all internal orders with a status of TECO, or technically complete). Statuses can be used as selection criteria (select all internal orders with a status of CLSD, or closed). Statuses can communicate the state of an object (ready for archiving, not ready for settlement execution).
There are SAP standard delivered statuses that apply to all object types. These are known as SYSTEM STATUSES. CRTD, REL, SETC, TECO are examples of SAP standard system statuses. SAP standard system statuses cannot be removed from use. You cannot override the SAP system status with a user status. You cannot change the behavior of an SAP system status.
User statuses (or user defined statuses) exist in addition to SAP standard statuses. User statuses are intended to augment or refine SAP standard statuses, not replace them. There is no limitation to the number of user statuses that can be created. Both system and user statuses influence business transactions in the same way.
An object can have multiple statuses active at the same time. A plant maintenance order can have released, preliminarily costed, work order printed and confirmed statuses all at the same time. For SAP display purposes only one status can be displayed on the status line in master data screens, but it is possible to see all active statuses for an object at one time by drilling down into the master data screens.
A STATUS PROFILE, or user status profile, contains individual user statuses and the business transaction rules defined for those statuses. There is no limit to the number of user status profiles that can be maintained in SAP. A user status profile is assigned to an order type or a project profile in configuration. This user status profile is then defaulted into all objects that reference that order type or project profile. A users status profile can be overwritten (or deleted) in an individual object (via native master data screens), but only if a user status has yet to be activated for that particular object. Once a user status has been activated for that object the user status profile cannot be changed.
HOW STATUS MANAGEMENT WORKS
When an object (internal order, WBS element, production order) is created SAP assigns the system status CRTD. MIT automatically releases the order, so the system status REL is also activated. If there is a user status profile defined in the order type (or project profile) this is carried over into the internal order (or WBS element). If not, only the SAP system statuses will apply to this object.
When a user executes a business transaction for this object, SAP checks the user status to see if that business transaction can be executed without any additional influence from a user status, can be executed but with a warning message being issued, or cannot be executed at all. SAP also checks whether the business transaction sets or deletes any other user statuses within the user status profile.
A user status may also be maintained directly in the object master data. Accessing the master data screens allows a user to manually maintain user statuses. If necessary, an authorization code can be assigned to a user status to ensure that no unauthorized persons can change the status of an object. Once changed, the new user status is fully active and acts no differently than if a business transaction set the user status.
Status management and business transaction control only work with standard SAP transactions. Z transactions will not show up on the business transaction list for an object. The business transaction table is configurable, but SAP strongly recommends not changing that table. SAP directly updates that table via support packs and it is often impacted during upgrades.
Authorization codes / keys are available in user statuses. The authorization code is checked only when user statuses are being set manually, from within the objectu2019s master data screens. This ensures the user has the proper authorization to set that status for that particular object. However, it is important to understand that SAP sets a user status in reaction to a business transaction it does not perform an authorization check.

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

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

Transaction VKM1 - Changes Sales Order Line Items Custom Fileds

Hi,
I have a challenge to indentify the impact of VKM1 on a Sales Order Line Item Customer Enhanced Fields. When credit hold for the customer is released in VKM1, I want to prevent some of the changes to the line items in the User Exit. The Problems I am not sure, How VKM1 is calling the Transaction VA02 or those Sales Order User Exits to modify certain customer enhanced fields. I tried Activation of Break Point in Update Task but did not stop at the Break points set up in the User Exit. How does Transaction VKM1 call the Sales Orders to execute changes? Is it through BAPI or Call Transaction VA02 or some thing else.
Can any One please help me? Appreciate Your Help in advance.
Thanks,
Kannan

VKM1 uses FM SD_ORDER_CREDIT_RELEASE to release orders on credit.

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 user status

Similar Messages

Maybe you are looking for