I wish to modify the name of one of the field name in the sales order.

HELLO GURRRUS,
i wish to modify teh name of one of the field name in the sales ordder.
what is the procdure,path and steps involved in that.it would be of great help of me if u take some time and suggest me.
bye take care hav a happy and peaceful life

Hi Sameer,
If you want to change the name or description of the field in the Sales order,
you have to use the userexit MV45AFZZ and use the Form USEREXIT_FIELD_MODIFICATION.
Get the help of the ABAPer and decide where do you want to make the change in the Header or the Line items. Accordingly give the requirements to the ABAPer.
He will do it.
Thanks
Augustine Ponraj

Similar Messages

Restricting modifying the Sales Order

Hi Expert,
Hope you can help on this...
I have to restrict specific user to modify the Sales Order where Series='SO-BOM', they can only modify this Sales Order with authorization from manager or from specific user....
Can i do this on TransactionNotification from StoredProcedure?
Thanks,
Richard

Hi Chard
You can insert this piece of script in Gordon's query by little bit change :
T0.DocEntry = T2.DocEntry inner join OUSR T1 on T0.UserSign = T1.USERID
where T0.DocEntry = @list_of_cols_val_tab_del and T1.USER_CODE != N'manager')
Giridharan V

How to modify the Sales Order Header Text

Hi Experts,
I have bulk of sales orders, for each sales order i have to modify the Header Text,( text id : 0005, text object = VBBK,)
for this, is there any standard BAPI or Function Module is available. If so could you let me know what are the input parameteres i have to pass.
Regards,
Nag..

hello,
there is BAPI "BAPI_SALESORDER_CHANGE"
there is a ORDER_TEXT in a table parameters in the BAPI.
pass all the relevant inputs & use commit bapi
Thanks,
Manjunath MS

Modifying the sales order status

Hi,
We would like to check the Customer master is in Restricted Party List or not, So after creation of order we would like to Hold the order until the check. So How to Control this? How to modify the order status?

Hi
Please check this for [Work Flow|PR Release Strategy + with Workflow;
Thanks
BVDV

Modifying Sales order in ECC does not modify the planned order in APO?

Hello,
I have the next situation, a MTO scenario, LPP material,:
- users create a sales order, quantity 2000M, 2 individual lenghts by 1000M. In automatically, being a MTO scenario, APO generates a planned order to fulfill the requirement with 2000 M qty, individual lenght 1000.
- users modify the sales order, the quantity 2000 M remains, but will change it in 1 individual lenght by 2000M. APO cancels the precendently created planned order and generates another one, with individual lenght 2000.This is OK.
-users modify the sales order, the quantity remains 2000 M, but again 2 individual lenghts by 1000 M. In this case, the planned order is not cancelled, as expected, but remains with individual lenght 2000, which is not ok.
Any idea how to fix this?
Regards,
Alex

Hello again,
while creating/changing sales order in crm,
the user exit mv45 is called in R3.
Problem solved.
Thanks
Gerd

Userexit to Restrict the VIEW and MODIFY of the Sales Order

Hello Everybody,
I need to do the following task.
I want to restrict to VIEW and MODIFY the sales order for particular sales office or sales group.
I need user exit for that.
Please help me by providing brief information.
Thanks
M Rahman

Hi Rahman
Instead of changing the DISPLAY and CHANGE status of Sales Order,
i think it would be better if u make a check at the time of SAVE.
When the SO is being saved in VA02,check the sales office or sales group
and then give a error message to the user, saying that he is not authorised to make changes to the
SO for this particular sales office or sales group.
For this you can use the inckude MV45AFZZ,and USER EXIT userexit_save_document.
Sample Code:
IF SALES_OFFICE EQ 'XYZ'.
MESSAGE 'Change not possible for this Sales Office' type 'E'.
ENDIF.
Regards
Hareesh Menon

Problem binding a matrix in the Sales Order Form

Hi everybody!
I am working in an Add-On. What I do is modify the sales order form in runtime. I catch the event when the form is loading and then I add a new folder with some fields and a matrix.
I've got a matrix in this form with the employees that participate in an order and when I go through all the orders by using the next and previous record buttons I have to rebind it to show the participants in a specific order. The code for the event is the following:
        If (pVal.ItemUID = "57") And pVal.Before_Action = False And pVal.EventType = et_ITEM_PRESSED Then
            BindParticipantGrid
            BubbleEvent = False
        End If
After bind the grid, BO shows a System message indicating that the form has been changed and asking me if I want to save the changes to the order. Looks like, whenever the bind function finds rows to add to the matrix it changes the mode of the form by adding rows to the matrix. How can I prevent that when I'm in view mode?
This is the code for the binding function
Sub BindParticipantGrid()
    Dim myForm As SAPbouiCOM.Form
    Dim oMatrix As SAPbouiCOM.Matrix
    Dim rs As sapbobsCOM.Recordset
    Dim strSQL, OrdreNr As String
    Dim oText As SAPbouiCOM.EditText
    Set myForm = SBOApplication.Forms.GetFormByTypeAndCount(139, 1)
    Set oText = myForm.Items("8").Specific
    If oText.Value <> "" Then
        OrdreNr = oText.Value
    Else
        OrdreNr = "0"
    End If
    Set oMatrix = myForm.Items("matrix").Specific
    oMatrix.Clear
    Set rs = myCompany.GetBusinessObject(sapbobsCOM.BoObjectTypes.BoRecordset)
    strSQL = "SELECT [@HL_PART].Code as Code, [@HL_PART].U_DocNum as DocNum, [@HL_PART].U_EmpId as EmpId, [@HL_PART].U_EmpName as EmpName, [@HL_PART].U_Message as Message, [@HL_PART].U_MessRead as MessRead, [@HL_PART].U_MainPart as MainPart, [@HL_PART].U_StartDt as StartDt, [@HL_PART].U_StartHr as StartHr, [@HL_PART].U_FinishDt as FinishDt, [@HL_PART].U_FinishHr as FinishHr, [@HL_PART].U_Finished as Finished FROM [@HL_PART] WHERE [@HL_PART].U_DocNum = " & OrdreNr
    rs.DoQuery strSQL
    While Not rs.EOF
        myForm.DataSources.UserDataSources.Item("EmpId").Value = rs.fields("EmpId").Value
        myForm.DataSources.UserDataSources.Item("EmpName").Value = rs.fields("EmpName").Value
        myForm.DataSources.UserDataSources.Item("Message").Value = rs.fields("Message").Value
        myForm.DataSources.UserDataSources.Item("MessRead").Value = rs.fields("MessRead").Value
        myForm.DataSources.UserDataSources.Item("MainPart").Value = rs.fields("MainPart").Value
        myForm.DataSources.UserDataSources.Item("StartDt").Value = rs.fields("StartDt").Value
        myForm.DataSources.UserDataSources.Item("StartHr").Value = rs.fields("StartHr").Value
        myForm.DataSources.UserDataSources.Item("FinishDt").Value = rs.fields("FinishDt").Value
        myForm.DataSources.UserDataSources.Item("FinishHr").Value = rs.fields("FinishHr").Value
        myForm.DataSources.UserDataSources.Item("Finished").Value = rs.fields("Finished").Value
        oMatrix.AddRow
        rs.MoveNext
    Wend
    oMatrix.SelectionMode = ms_Auto
End Sub
I will apreciate all king of help
Thanks in advance.

You have a property of the form which allows you to change the mode
myForm.Mode = fm_ADD_MODE
myForm.Mode = fm_EDIT_MODE
myForm.Mode = fm_VIEWMODE_MODE
You may change it after you modify you matrix data to fm_VIEWMODE_MODE and I guess you won't have the system question again.
Sebastien

Modifying the production order from VBAP

Hi Expers
I need some modification and write a code so how to proceed with the following comments as below
Modification to processing of Command Orders & Tickets
Currently there is an assumption that every sales order (and its deliveries) will include a product which is made to order, i.e. for which a production order will be required.
In ZINT_CSTPORD_ROUTINES, a check is made to identify the production order linked to the sales order. If there is no such production order (usually because of the customeru2019s credit status) then processing of the ticket is terminated.
This assumption would fall down if an order was to be raised (in Command) on which there is no concrete material. For example, if we sold a bag of pigment or a screed to a customer. In this case the item would be sold from stock and there would be no need for a production order.
The solution
In the routine which checks for the existence of a production order, modify the code as follows:
u2022 Inspect each item on the sales order
u2022 If (and only if) there is at least one item with a category of u201CZTACu201D then check for a production order, otherwise process the order in the usual manner.
Regards
Piroz

Thread closed

Free Good Qty as non modifiable field in the Sales Order Level

Dear Friends,
I have successfully done the config change for the Free Goods, But now i want make the free good line item qty as a non modifiable field in the Sales Order Level.
How can i do this.. Please advice.
Thank U,
Uwanthi

Hi
This is a standard behaviour in the system
kindly use the below program and user exitexit
MV45AFZZ and use "Userexit_filed_modification"
Regfards
Damu

Add the carrier description/name on a sales order

On sales order in Tax tab when a carrier is selected, it´s only shown the field with carrier cod without his description/name.
How can I add the carrier description/name on a sales order?

Marcio,
This should be simple.
Save this SQL Code and attach it to the Transport Name User field / any other field where you want the shipping name.
SELECT T0.[TrnspName\] FROM [dbo\].[OSHP\] T0 WHERE T0.[TrnspCode\] = $[ORDR.TrnspCode\]
When I use $[ORDR.TrnspCode\] it refers to a field value on the form. I am presuming this is the field you are using. If your TrnspCode is in a different field. From the View Menu click System Information. This will enable you see the table and field information on the Status Bar
Use this information instead of $[ORDR.TrnspCode\]
Suda

How to find the Sales Order Overall Status (VBUK-GBSTK) modified Date?

Hi Experts,
A Sales Order could get automatically closed at the point of Packing or Invoicing, At this point the field GBSTK in table VBUK turns to status 'C' means Closed. This could also happen when Sales Order Line Items Rejection Reason is filled.
I want to find the Date when GBSTK got modified in this way I would know the exact Date of the Sales Order Close. At the moment this is not shown in Sales Order (VA02, VA03) or in the table VBUK. I have searched everywhere to locate the Date. I need you help.
Thanks,
Sri

Although VBUK is mentioned (Tx SCDO, Tab TCDOB) for the ChangeLog Object VERKBELEG, you won't find anything in CDHDR due to the fact that Data element GBSTA's Log-Frag (DD04D-LOGFLAG) is not switched on.
For Workaround you might try Audit Trail
Audit Trail (electronic records) / Tx AUT10, AUT01, XX-PROJ-ELR, OSS 564743,517613,564645
OSS 1058984 - FAQ: Audit Trail (Transaktionen AUT01-AUT10)
http://help.sap.com/erp2005_ehp_03/helpdata/DE/fc/89683c1b5fb712e10000000a114084/frameset.htm
Cheers
carsten

User Exit in the Sales order create BAPI

Hi,
Can some one help me in telling if there exists a user exit for the BAPI '/AFS/BAPI_SALESORDER_CREATE'.
This is urgent. So, pls. throw some light on this.
Thanks in advance.

Hi
User Exits In Sales Document Processing
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.

Dates fields issue in the sales orders through IDOC

Hi all,
I'm trying to create a sales order through Inbound IDOC using IDOC_INPUT_ORDERS.
I have 2 custom fields in the sales order which are date fields.
I'm populating them from the IDOC segments(using E1EDKT1-tdid, E1EDKT2-tdline) in the user-exit just before the call trasacation statement. These dates are not coming for a few orders... but are getting populated normally for few of them.
But the tricky part is that... if I process the same IDOC for the second time.. the order created is having the dates.
My issue is that.. i need all the orders to be populated with the dates which IDOC have.
Could anyone please help me with this issue.
All the answers/replies are highly appreciated!!
Thanks for you help!

hi,
the following may be of help
There are 2 major exceptions to the batch input internal table. All text data from the segments E1EDKT1/2 and E1EDPT1/2 are not part of the batch input session. Text elements from these segments are posted directly to the data base AFTER the sales order has been created (please note: in order that item texts are posted correctly to the sales order the field POSEX from segment E1EDP01 MUST be transmitted). Also, configurable material information from the IDOC is exported to a global memory and therefore will not be part of the batch input session. Configurable material data is performed in Form CHECK_CONFIGURATION and the data is exported to global memory in the following code:
Exportiert IDOC Daten ins globale Memory
export IDOC data to global memory
call function 'CUXC_IDOC_TO_MEMORY'
       tables
            cfg_instref = xe1curef
            cfg_ref     = xe1cucfg
            inst        = xe1cuins
            part_of     = xe1cuprt
            value       = xe1cuval
       exceptions
            error       = 1
            others      = 2.
One extra piece of useful infomartion if you wish to debug the process is to set your breakpoints at the following points
for Function module IDOC_INPUT_ORDERS
include LVEDAF0F..
CALL TRANSACTION 'VA01' USING bdcdata
                            MODE input_method
                            UPDATE 'S'
                            MESSAGES INTO xbdcmsgcoll.
Now input_method is A foreground process and N for background processing but try changing it to P (pass through mode)
If you have breakpoints in va01, e.g. MV45AF0B_BELEG_SICHERN,(the part where the sales document is saved)
they will be hit, e.g
perform userexit_save_document_prepare.
perform userexit_save_document.
Lastly, don't forget using program SDJEDI , see note 380603 for more information on this
Hope this is useful
Paul Quinn

Hi All, We are in to Release 11.5.10.2.There is a specific requirement to Prevent users from creating Manual Sales Orders in oracle and yet users should be able to book the Sales Orders Imported from CRM system into Orcale.Please advise.

Hi All, We are in to Release 11.5.10.2.There is a specific requirement to Prevent users from creating Manual Sales Orders in Oracle and yet users should be able to book the Sales Orders Imported from CRM system into Orcale.Please advise.

Thanks for your advise.
However, I missed to mention that we have two set of users One is for Finished Goods and another for Spares.
Only Spares users need to be prevented from creating Direct/Manual Sales Orders in Oracle.
As you suggested, if this will be done at Form level, that may Disallow FG users also to create Manula Sales Orders which should not be the case.
Further, I tried to test one scenario through Processing Constraints but it did not work.
Application
OM
Validation Type
Entity
Temp
Short Name
TBL
Validation Semantics
Created By
Equal To
User(Myself)
Processing Cosntraint
Application
OM
Entity
Order Header
Constraint
Operation
User Action
Create
Not Allowed
Conditions
Group
Scope
Validation Entity
Record Set
Validation Template
101
Any
Order Header
Order
Above Created
Please advise.

Erroneous Shipping Header Text in the Sales Order

Hi ,
We are facing one problem.Can you please help us..
We seemed to have a recurring issue in SAP Production wherein an erroneous shipping text and supply location header text
suddenly appears on the sales order header text.   As of this stage, our interim solution is to manually clear the erroneous text via invoking
the SAVE_TEXT command directly in Production to clear out the text.   The problem with this approach is that we are "reactive"
to the event meaning we only get to know of the issue after the National Order Centre reports the issue and by the time it reach
IT it already affected quite a few sales and stock transport orders.
I
a) an investigation to be conducted as to identify the root cause of this issue
b) permanent solution to be put in place to rectify the issue
here's the text ID that got affected
Text ID = Z022 (Shipping Text)
Text ID = Z029 (Supply Location)
Language = EN
Text Name = XXXXXXXXXX
Text Object = VBBK
a list of programs that calls SAVE_TEXT and updates
the above-mentioned text ID. We have gone through the SD user-exit MV45AFZZ.
The sample you see below is an STO. As you know the STO is created inside the sales user-exit and uses the
shipping instruction default from the originating sales order to pass on the text to the STO shipping text.
We are unable to re-create this issue so this sorts of adds a layer of complexity.
I found SAPLSTXD memory id..It is importing from this id..But there is no export in the program..
Can you please help us where the text is exporting ..We need to find out the root cause of this issue and solution..
Thanks in advance.
Satish kumar.

I found SAPLSTXD memory id..It is importing from this id..But there is no export in the program..
Chances are it is set and exported at some point, then abandoned after processing for that document...it needs to be cleared probably, since your user is remaining in the same user context and therefore when another import is executed, the text stored there is brought in, even though not for that order/document....believe you'll find this is a programming error, need to export space or clear the ID after it is used...
Check the other MV45AFZ* objects also...MV45AFZZ is not the only SD user exit...look at the inlcudes (named like mv45afz* ) in SE80 for program SAPMV45A. I can't see SD (don't run at my employer), but you might also check copy requirements in transaction VOFM entries? Some of the SD wizards can advise on that part.
Try ABAP Scan program RSRSCAN1, probably as background job, if you don't find in MV45AFZ* members. Sorry, that's the old program (but it might find for you). Current version is program RPR_ABAP_SOURCE_SCAN.
Edited by: BreakPoint on Sep 22, 2010 4:16 PM

I wish to modify the name of one of the field name in the sales order.

Similar Messages

Maybe you are looking for