Created by field determined in sales order creation

Hi,
I am trying to integrate SAP with a third party program. Sales orders are created by idocs but I want to differentiate the sales orders created by interface from the orders created in SAP directly. So I created a user id as RFCUSER. I want to show this in the sales order header sales view created by field (VBAK_ERNAM) How can it be automatically determined when a sales ordr created by an idoc. I can not send this information in the idocs as I see?
Thank you

Hi,
You can check it in this path:
- System / Service for an object / display relations.
I dont know the tables and programs but if you do a trace surely you will know how to do it.
Regards,
Eduardo
PD: the name of the author is the name of the user ID that run the reports that create the idocs and so on.
Edited by: Eduardo Hinojosa on Sep 7, 2009 3:45 PM

Similar Messages

Create ecatt script for one sales order creation with multiple line items

Hi ,
I want to create a ecatt script for one sales order creation with multiple line items. Preferably SAP GUI.
This selection of data will be from an external file/ variants which will have only one row of data in it.
Firstly: I have to sort the external file having same PO Numbers in an order.Group them together.
Second: I have to create sales order for those many line items having same PO Number.
Best Regard
Taranum

Hi Micky
Firstl you should upload the Line items for a particular sales Order in an Internal table
and then pass that internal table to your BAPI during your coding corresponding to a particu;lar sales order
In case of any issues pls revert back
Reward points if helpful
Regards
Hitesh

Route determination during sales order creation!

Hello all,
I am having a problem with route determination in sales order. The issue is when I remove delivery block (LIFSK) on the sales order and select 'under minimun' in orther reason (AUGRU)field, the route is not getting determined when the partner at the header level is changed.
When if there is a delivery block and other reason is empy, the route is correctly determined when the partner (intermediate consignee) is changed.
Why is it behaving this way? Any siggestions?
Thanks,
Message was edited by:
Naren Somen

Hello all,
Looks like if there is credit block for a customer, the sales order is not getting updated. Is there anyway to get around this?
Thanks,

Item Category Determination during Sales Order Creation

Dear All,
This is Chee Wee, i'm new to SD, i would like to seek for an advice for the topic related to Item Category in Sales Order.
We have a material "Mat005" define as "Stocked" Item category in MM03,
*Stocked means our MM team will always keep stock for the material.
The document Item category assigned to this "Stocked" are "NoPo" --> No Auto Po creation and "AuPO" --> AutoPo creation.
During the SO creation for Mat005 with Qty50 and warehouse stock availale for 60, i'm wondering when i select the itemCat "AuPO", the system automatic changed to "NoPO", but when i change the order qty to 70, then i'm able to changed the itemcat to "AuPo"!!
Can any Guru advice me what is the actual setting or configuration behind to determine which are the correct Item Category that i can choose?
Thank you very much,
Regards,
Chee Wee

Dear Chee Wee,
Basically tem category will determine based on these key combination
Item category group(Material master)+Sales document type(We enter doc type in the creation initial screen)--->Item category
For Example NORM+OR--->TAN.
As per your explanation
I hope In your case stock availability also one of the factor in the item category determination.This might have done some enhancement.
There are two item categories in your process one is "NoPo" --> No Auto Po creation and second one is "AuPO" --> AutoPo creation.
the system automatic changed to "NoPO", but when i change the order qty to 70, then i'm able to changed the itemcat to "AuPo"!!
60 Qty Stock available, you have created sales order for 50 Qt here requirement is less than stock availability so system will not allow you to enter AuPo item category Because there no need of auto PO creation for stock.
When you created sales order for 70 Qty, stock available only 60 so there is shortage of 10 Qty.now system needs to allow to create Auto PO to procure the shortage stock of 10 Qty, so system is allowing you to enter Yaupon item category.
There might be some work around kind take help of ABAPer to get the more details about your item category determination.
I hope this will help you,
Regards,
Murali.

Automatic identification of contracts in sales order creation

Hi,
I have configured quantity contracts as a automatic determination during Sales Order creation .When i try to create sales order using va01, after i enter Sold-to Party and Material then i hit enter ,system pops up with a dialog box with list of all the contracts existing with that Sold-to Party and Material combination.
Can someone suggest me , is this pop -up window is a User Exit? If so . can you pls let me know .
I went to program SAPMV45A , which has many includes and try to check the include MV45AFZZ , but could not find out the one which i want for Pop up window.
Thanks in advance
Points are fully rewarded

Hi,
If it is a standard sap configuration..Then it may not be a user exit..
After entering the sold -to party ...Then press /H in the command button..
Then start debugging..You might the call.
OR
after the popup is displayed..Press F1 on any one of the field..In that help..press technical info button...Then check the program and screen number..
Go to SE51 with the program and screen number.Then press the where-used list button to get the calling place..
Thanks
Naren

Sales Order creation/ change date for the items

I have a unique scenario and i need to get a Report for this
A sales order is created for 4 line items.
Out of these , for 2 line items a delivery is created. I need the sales order creation date and time for these 2 items in a custom report
Now the other 2 items go in to some kind of block- Now these are released by going in the sales order VA02 and after releasing the delivery is created. Again for these two items , i need the sales order change date as after a user goes and changes the sales order to remove the block only then delivery is created for these two items
Also another scenario is the 2 line items go for back order and when we get stock at tht time system confirms the stock and then the delivery is created for these. So also for this when this change occured i need to get the date for these 2 line items
Can any one please suggest how to get this data from the scenarios?
I dont want to get the date when the delivery is created as i can get tht from the LIKP table. I need the sales order create and change dates for these.

You may be aware, any changes to a document will be recorded in CDHDR (for header changes) and CDPOS (for item changes). You can explore these two tables.
thanks
G. Lakshmipathi

Sales Order Output - determined by Sales Order Type, Created By

I want have my order output determined by sales order type
(vbak-auart) and created by (vbak-ernam).
I have created a condition table 501, access seqeunce Z001.
In v/48, in accesses for Z001, I created
AcNo: 10
Tab: 501
Requirement: [empty]
Exclusive: unchecked
in fields, I can't find ERNAM in structure KOMKBV1(header), but I find one in KOMPBV1 (item).So I have assigned it to ERNAM.
besides, I have created the corresponding records in VV11
I expect to have:
Output Z001 will be created for sales order type OR if created by user XXX
However, no output is generated. When I go out detemination analysis, I found that in the output determination procedure, it did go into output type Z001, but, since no value is found for "created by", i got message "Access not made (initialized field").
I suspect that no value stored in KOMPBV1-ERNAM. Do you know how I can get it done?
Points will be awarded for useful information. Thanks in advance.

Hi
You have to include this field as a Zfield in the structures KOMKBV1, KOMPBV1 and KOMB.
You have to include the field as Zfield in these structures.
Once this is done, you should also be able to update this field in the structures.(As on now, you have only created a field, but you have not mentioned how the field has to be updated.
In order to update the logic, you have to do a small code in one of the user exits for outputs.
In the user exit, you have to write a code like this
MOVE VBAK-ERNAM = KOMKBV1-ZERNAM(this is the zfield you have created)
Now create the condition table and do the rest.
Your output should work fine. The user exit I was saying is the subroutine USEREXIT_KOMKBV3_FILL in the include RV61B902 in the user exit RVCOMFZZ. If you can give this info to the technical guy, he should be able to find out the same for saels order output also.
The user exit RVCOMFZZ also has the subroutine USEREXIT_KOMKBV1_FILL which you can verywell use for your requirement. This will solve your problem
Hope this helps.
If you have any problems in this, you can again put the problems in this thread. I will try to solve.
Reward if this helps you

One Time Customer Mandatory field during Sales Order Creation

Hi
My client has lots of one time customer and they need to capture the phone number and name of the individual customer at the time of sales order creation using one time customer code.
They want only "NAME & PHONE NO" as mandatory field so that the Person who creates a Salesorder should enter the NAME & PHONE NO" . Please let us know where the configuration for teh above is?
We have tried in Account Group One time customer settings which is working at the time of creation of order and not at the time of creation of Sales Order, please help us on the above..
Regards
Anis

Hi Anis,
In the Account group , if you check the one-time customer then while creating the sales order itself it will appear to change the address for that customer.
By the time you can enter your required fields.
I think you mentioned as
We have tried in Account Group One time customer settings which is working at the time of creation of order and not at the time of creation of Sales Order, please help us on the above..
Order creation and creation of sales order are both same.
May be you would have confused.
regards,
santosh

User exits for route determination in Sales order & Deliver creation

Hi Gurus,
I need to do some change in the route determination for both sales order & Delivery creation.
Can anyone suggest me which user exit I have to use.
Appropriate answers will be awarded.

Hi,
You can use the following exit for route determination - EXIT_SAPL0VRF_001.
The FM documentation is below. Check the functionality:
"The customer exit can be used for customer-specific route determination or to modify the inbound data for the company's own route determination.
The following data is transferred to support customer-specific route determination:
I_VBAK current order header (for route determination in sales order)
I_VBKD order business data (for route determination in sales order)
I_VBAP current order item (for route determination in sales order)
I_VBPA current sales partner
I_LIKP current delivery header (for route determination in delivery)
The following data can be modified and transferred back to the standard route determination or used for a specific route determination:
C_ALAND Country of departure
C_AZONE Departure zone
C_LLAND Destination country
C_LZONE Receiving zone
C_VSBED Shipping condition
C_TRAGR Transportation group
C_GRULG Weight group
C_FLAG_GEN_VT Flag: Route determination with generic shipping
requirements/transportation group.
C_FLAG_INCR_GRULG Flag: Increase weight group if no route
If you want to use a standard route determination with different parameters, trigger the exception 'CONTINUE_WITH_STANDARD'.
In the log table C_PROT, the log data from the customer-specific route determination can be transferred back. In this case, the log entries always refer to customer-specific messages. To add a message to the log table, the function module SD_ROUTE_DET_LOG can be used (see below).
If a route is determined in the customer-specific route-determination, it can be transferred back in the E_ROUTE field. If no route was found, the exception 'NO_ROUTE_FOUND' is to be triggered."
Thanks.

How to create a daily report for sales order

hi
how to create a daily report for sales order. what fields it must consists of. what are the tables it need?

Hi
You have to use the sales order tables VBAK,VBAP and VBEP
So keep date field on selection screen
and treat this date as Order creation data audat field in VBAK.
based on this fetch the data from VBAK and VBAP with the following fields like
VBELN, KUNNR,NETWR,POSNR, MATNR,ARKTX,KWMENG,WAERS etc and display in the report
<b>Reward points for useful Answers</b>
Regards
Anji

BAPI - Problem in Sales order creation

Hi Friends,
I have problem in Sales order creation using BAPI ,I am getting a messsage - Error in creating document ,I have sent the code along with this mail ,can you help it out.
Code:
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
PARAMETERS: p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Sales organization
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Distribution channel
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Division.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Sold-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Ship-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Material
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Quantity.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Plant
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Data declarations.
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead1.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapisditem OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                         WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                         WITH HEADER LINE.
Initialization.
INITIALIZATION.
v_text   = 'Order type'.
v_text1 = 'Sales Org'.
v_text2 = 'Distribution channel'.
v_text3 = 'Division'.
v_text4 = 'Sold-to'.
v_text5 = 'Ship-to'.
v_text6 = 'Material'.
v_text7 = 'Quantity'.
v_text9 = 'Plant'.
Start-of-selection.
START-OF-SELECTION.
Header data
Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
Partner data
Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
Ship to
partner-partn_role = 'WE'.
partner-partn_numb = p_ship.
APPEND partner.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
Call the BAPI to create the sales order.
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
       EXPORTING
            sales_header_in     = header
            sales_header_inx    = headerx
       IMPORTING
            salesdocument_ex    = v_vbeln
       TABLES
            return              = return
            sales_items_in      = item
            sales_items_inx     = itemx
            sales_schedules_in = lt_schedules_in
            sales_schedules_inx = lt_schedules_inx
            sales_partners      = partner.
Check the return table.
LOOP AT return WHERE type = 'E' OR type = 'A'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0.
    WRITE: / 'Error in creating document'.
ELSE.
Commit the work.
    COMMIT WORK AND WAIT.
    WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF.
Regards,
Dinesh

what messages u are gettting in RETURN ? Please check the RETURN tables data.
[code]CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
EXPORTING
sales_header_in = header
sales_header_inx = headerx
IMPORTING
salesdocument_ex = v_vbeln
TABLES
return = return
sales_items_in = item
sales_items_inx = itemx
sales_schedules_in = lt_schedules_in
sales_schedules_inx = lt_schedules_inx
sales_partners = partner.
Regards
Prabhu

Pricing procedure determination in sales order

Hi Experts,
In our business scenario, we have three plants and all plants have different pricing procedure. And we are using same sales area and sales document type for all plants.
Currently one customer is purchasing goods from only one plant. So in our system, pricing procedure determination in sales order based on customer pricing procedure.
Now as per new requirement, same customer will purchase goods from different plant. And we can’t change or create new sales area and sales document type as per our existing system design.
So can we change customer pricing procedure at a time of SO creation level? If yes than how?
Regards,
Haresh

Are you a functional or developer?
Hope are aware that as per SAP standard, pricing procedure(OVKK) is determined based on
(1)
Sales Org
(2)
Distribution Channel
(3)
Division
Customer Pricing Procedure
(5)
Document Pricing Procedure
Sales area determined in your sales order or billing doc
Determines from Sales Data of Customer Master
Determines from sales(VOV8)/billing(VOFA) doc type
In addition to that sales order is created for only sales area, which you select based on your customer sales area while creating the sales order.
Now, keeping above facts in mind, can elaborate your requirement again.
Thanks, JP

How to make all fields mandatory in sales order T- code VA01 initial screen

Dear all,
how to make all fields mandatory in sales order T- code VA01 initial screen itself
The fields are
Sales Organization
Distribution Channel
Division
Sales Office
Sales Group
Regards,
Amar Reddy

Hi,
You can use Transaction Variant to achieve this functionality.Please go through the following link which helps you in creating the same.
[Link|http://wiki.sdn.sap.com/wiki/display/Snippets/TransactionVariant-AStepbyStepGuidefor+Creation]
Regards,
Phani Prasad

Item Category determination in Sales Order

Hi
How to know, how item category determined in Sales Order. Is there any analysis available in Sales Order level, similar to output or text determination.
Problem here is in a particular sales order, item category is different compared to configuration. Nothing is recorded in change log. How to know, whether system determined this item category or user changed manually.
Regards
Uma

Hi
Problem here is in a particular sales order, item category is
different compared to configuration
I cant take this arguement
Sales order item cate will picked via the config maintained in VOV4
item category is different compared to configuration
Configuration someone might have changed after that sales order created
Nothing is recorded in change log. How to know,
whether system
determined this item category or user changed manually.
During order creation if you are inputting the allowed manual item category manually in salesorder then that is not a change
Hence it doesnot get recorded (VA01 T code)
During order creation a default item cate gets determined if you chnge that to manual, then that is also not a change
Hence it also doesnot get recorded (VA01 T code)
But in VA02 if you change the item category manually then it is recorded in change log
No item category determination analysis is available in standard and not reqd too
In your case only this could have happened
Configuration someone might have changed after that sales order created
Regards
Raja

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
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.
Regards
Eswar

Created by field determined in sales order creation

Similar Messages

Maybe you are looking for