Condition Value(KONV-KWERT) for Sales Order

Hi Experts,
I have to print the condition value for ZTDC Condition Type from Header Value, currently it is getting the data from line item level. I am getting condition no document (KNUMV) from VBAK table and checking that condition no document in KONV table to retrieve the Condition Value(KWERT) but it is picking item level data.
We need to get the condition value for the header level.
Please help me.
Points will be rewarded for useful answer.
Thanks,
Vinay.

Hi!
Try using table KONP (condition at position level) and KONH (condition at header level).
Regards
Tamá

Similar Messages

Conditions KONV table for Sales order Line item.

Hi Friends,
What are the key fields bw vbap and konv table.
requirmnt is : need to fetch conditions ( from KONV table ) for the sale order line items.
thanks in advance.
Jai.

Hi,
1. Fetch field KNUMV from table VBAK for that particular Sales Order No i.e VBELN.
2. Goto KONV & based on KNUMV, KPOSN and KSCHL (condition type), fetch the required condition details along with its net price (KONV-KBETR) and net value (KONV-KWERT).
KONV-KPOSN = '00000' -> Header Condition
KONV-KPOSN = '00001' -> VBAP-POSNR = 10
Reward points if the answer is helpful.
Regards,
Mukul

Condition value is Inactive in sales order

Hi Friends,
I am facing the following problem,
In the sales order, it is picking all condition records as per pricing procedure and calculates perfectly. But in the header net value field it is not updating. It is showing one condition record value only.
During analysis I found that the all records is inactive except which one is updating in the net value field and reason is "Y - Inactive because of Subsequent Price."
Please help me to solve this issue.
Thanks in Advance.
Dilip

Dear Dilip
For information, when you have a condition record showing as
inactive it is because you have a base price condition record
somewhere below your discounts.
Check your condition records below the discounts, are
there any of condition class 'B'? If yes, then that is why they are inactive.
thanks
G. Lakshmipathi

Statistic condition values not updated during Sales order Settlement

Hi,
In our client we have different Price condition types for based on scenario wise. Ex: Domestic Sales (ZPR1) and Export Sales ZPR2. I have maintained separately value fields for each price condition types.
We are booking some financial charges, and interest on working capital etc., this cost we need to transfer to COPA each Material wise based on sales revenue.
For this purpose we have created one COPA Assessment Cycle. Tracing factor is Sales Revenue and receiver is Materials.
In COPA Assessment cycle we can give only one base means ZPR1 related value field or ZPR2 related value field.
For this reason we have created one new statistic condition type, what is amount there in ZPR1 that amount will updated automatically in statistic condition place and so that we can give once one trance factor in COPA Assessment Cycle. We have assign this statistic condition all pricing procedure
Now my problem is in MTS scenario statistic condition values updated correctly. But in MTO scenario sales order settlement time statistic condition values not updated.
So is it possible update during sales order settlement time statistic condition values.
Please give me suggestion.
Regards,
Thiru

Hi Ajay Sir,
As you said is correct.
But in our client we have around 9 Plants and each plant manufacturing product are different. Client Requirement is in COPA Report they need see each product wise sales revenue. In this way we mapped product wise value field. System already mapped one guy in this way earlier. Now I am doing some changes for relevant to month end activities.
Some financial changes transfer to COPA each plant wise on Material. Here sender is cost center and receiver is Material. Base is Sales Revenue.
Please suggest me is there any alternative.
Regards,
Thirumalesh .

Can I have mannual condition value as zero in Sales order

Hi
I need to enter a mannual condition type in sales order in %, but it should not give me any value and it should be zero. In Pricing procedure I haven't maintained any values in from & to column, but then it is taking the value either from the base price or from some other value. Can any one tell me how to control this....and get zero as value in sale order though I enter in %.
Regards,
Ragu

Hi,
What is the function of the condition type if its effect is not to be evaluated in the pricing screen.
anyways if thats the case, in the pricing procedure you can specify the counter no. in the from and to fields related to the condition type.
you can enter the counter no. of the base price on which you want the percentage of the particular condition type to be executed.
hope it would solve your problem.
regards,
Siddharth.

Searching for Sales orders with a particular condition type..

Hi,
I'm searching for sales orders and purchase orders which contain a particular condition type, can someone please point me in the right direction?
Regards,
Attiq

Hi,
Goto SE16 and put KONV
Put the particular condition type that you are looking for and execute
Copy the KONV- KNUMV value for all the records found
Goto SE16 and put VBAK / VBRK
in the field VBAK-KNUMV or VBRK-KNUMV put the copied data from step three and execute
Note all the corresponding document number i.e. VBAK-VBELN / VBRK-VBELN
Pls reward if helpful.
Regards,
Pramod.

Fetch Vat and Octroi value for Sales Order Smartform .

Hi all ,
I am using a copy of /SMB40/SDORC_A smartform for sales order creation . I have to pass the vat and octroi of individual item as well as on the final total and then give the final bill amount . Can anyone please tell bewhich fields should i use and which areas do i need to do the changes in the smartform.

Hi Disha,
From the billing number VBRK-VBELN, pick the value of VBRK-KNUMV and pass this to KONV-KNUMV and display the value of KONV-KWERT against KSCHL
Regards..
Palaniayppan subbiah

Header condition type value not displayed in sales order output

Hi gurus,
I have observed a strange issue regarding a header condition in a sales order.
we have a set up like following:
1. If the Header condition XXXX is used in sales Order then this value should be printed on sales order output.
2. If the Header condition mentioned in above point is not maintained in sales order it should print the total price of all line items.
Though i have maintained the header condition value in Sales Order Header its not displayed in SO output.
That is , I have a sales order and it has one HEADER condition type entered with 3500 USD.
In fact this value is used for some business purpose and is being printed on the sales order output for a specific output type.
But where as in a sales order this header condition value is not getting printed on the output though I am using same data as of the sales order which is having the header condition value printed on its output.
According to business,we must have the header condition value printed on sales Order output.
Please suggest how to proceed.
Thanks in advance.

Not sure if you are using costom smartform to print invoice, if yes then ask developer to debug and find the root cause and fix it.
You might need to give him condition when it shuld be printed and when not.
You can take reference of another output type for which it is printing

Surcharge rate for sales order item condition

Hi,
I have a two condition for sales order item.
First condition is ZP00-Price. It is using for automatically price with customer and material. It linked with account key in pricing procedure.
Second condition is ZI00-Index rate. Calculation type is A-Percentage. This condition value is monthly. It will be used for surcharge with percantage . I have a formule this condition.
It is not linked with account key in pricing procedure.
Formula for ZI00 - Index rate:
(Index Rate to delivery date - 1 / Index Rate to contract start date) x 100
For example;
Index rate conditions is entrying monthly;
Index date          Index%
01.08.2008         1,05
01.09.2008         1,15
01.10.2008         1,17
Contract start date = 03.08.2008
Delivery date = 02.10.2008
ZP00 = 500
ZI00 = Index rate for sales order item = ((1,17-1)/1,05 ) * 100 = 16,19
Last condition value = 500 + (500 * 16,19)/100 = 500 + 80,95 = 580,95
What can I do for this pricing?
Best Regards
Gulay Celik

Hi
I think that perhaps it is too late. The application supports cancellation and re-billing as separate transactions. Maybe this is not a 'development' problem.
Cheers
Dom

BAPI FOR SALES ORDER PROBELM IN PRICING VALUE

Respected Members
i have a problem in creating sales order through BAPI
i will explain you.
My flat file structure is
doc_type sales_org dis_Ch division part_num pono itm_num material short_text qty plant price
OR 1000 20 10 1000 123 10 100-100 abc 50 1000 500
OR 1000 20 10 1000 254 10 100-200 XYZ 70 1000 800
Now when i am executing my program with this flat file data , everything is coming but problem is that in second sales order which is getting create is also having the quantity and price value of the first sales order ie 50 and 500 and it is not taking quantity as 70 and price as 800.
Rest everything is getting changed .
For eg Material is getting changed and description is getting changed for second po.
for second sales order it is taking material 100-200 and description XYZ only.
Then why it is taking values for quantity and price same as first sales order.
i m using the bapi function module in the loop only and thats why two sales order are getting generated.
also at the debugging when the values are passed to BAPI function module it is passing the correct values ie 70 and 800 but finally when i am going to tcode VA02 and seeing the sales order then it is showing the values of the previous order.
Please give me the solution as soon as possible.
Thanks

Hello Manish,
If you are calling the BAPI within a loop, try to put the BAPI_TRANSACTION_COMMIT within the loop as well so every order is commited properly before the next one is created.
Hope that solves your problem.
Michael

Dectivate pricing condition for sales order not service order.

Hi,
We are on ECC6.0 and CRM5.0
I need to add new condition type to the existing pricing procedure.It should be activtaed only for service orders and not for sales order.I can achive this by adding new requirement in pricing procedure to limit this condition type based on order type.
Example: if KOMK-AUART eq ORDER_TYPE.
sy-subrc = 0.
But I don't want to do this,because I would need to change this requirement everytime I add new service order type.
Is there any field in Pricing structure KOMK bu using which we can achieve this. ?
Please suggest any other idea by which I can achieve this
Thanks
Dona

Currently ,we have one pricing procedures for both the scenarios...
We control if the perticular condition type to be active or not by writing a requirement which checks the order types.
This has been done this way because we built the pricing procedure in ECC and tranfer it to CRM.Also we donot have service orders in ECC.
any further alternatives guys..

Condition for sales order delivery block

Hi All,
I am new to Workflow,
I have created work flow for Sales order changes, its works fine.
but my requirement is after that it will check whether sales is block for delivery or not.
if it is block then only it should send mail.
Regards,
Arpit

Hi Arpit,
1. Go to t-code SWO1.
2. Click Settings -> Delegate.
3. Delegate the BO YBUS2032 to the BO BUS2032.
In workflow perform the following steps:
1. Go to t-code SWDD and open your workflow template.
2. Go to Basic Data (cap sign button at the top of the screen) or click Ctrl + F8
3. Go to Start Events tab.
4. In the Object type enter your BO name BUS2032 (not YBUS2032), in Event of object enter the BO event.
5. Click on 'B' i.e. Binding Defined, click on generate automatic binding. It would automatically generate the appropriate binding for the workflow. You can also alter the binding as per requirement.
6. Click on 'C' i.e. Start Condition. A dialog would open, select the appropriate start condition for the workflow. Use the attribute that you created and make the start condition. Check the condition before saving (recommended).
6. Click on 'A' to Activate the binding and start condition. All 'A', 'B' and 'C' would get green.
7. Save the changes made and activate your workflow.
Hope this helps!
Regards,
Saumya

COPA - Flow of values for Sales Order

Team,
We follow the process of creating an Inquiry and sales Order leading to billing. Values were flowing from Sales order properly when we were not creating the Inquiry. Now when the Inquiry is created , SO values are not flowing. When we run the post processing for transfer of values COPA says error message says " Create a Sales Order " for the inquiries which do not have SO. Where the SO's have been created - system says its duplicate and cannot be posted.
Bottomline - SO values are not flowing to COPA.
Please advise...
Cheers
Kartik

Hi Karthik,
I gues you are getting error KF755 in your process.
Please first check the Long Text of error message KF 755:
Sales document "" was not transferred to Profitability Analysis (CO-PA) because it is not relevant for the analyses in CO-PA.
This can be due to one of the following reasons (among others):
- The document type is not profit-related, such as an inquiry.
- The sales document shows zero for the quantity.
- The sales document has been denied.
- The sales document is locked due to credit reasons.'
Please also check the attached notes 592231 and in particular note 20254.
In case of make-to-order process the invoice will be assigned to the sales order and will not be directly transferred to COPA. With the order settlement the costs and the revenues (invoice) will then be posten to COPA.
That means that in this case CO-PA is not updated during invoicing but via transaction VA88 for the sales order linked to it.
You can check this if you look at table VBAP (for the relevant sales order). If the field KZVBR is set to 'E' the invoice belongs to an make-to-order process.
Best Regards,
Abhisek Patnaik

Additional selection Condition for sales order in CFM1

Dear APO Gurus,
Our business scenario requires CFM1 to have additional selection
condition based on Sales order type (Table:VBAK, Field: AUART) for
sales order data.
Kindly guide us if there are any enhancement or OSS note to acheive the
requirement?
I know OSS note: 507696 can be used for enhancing CFM1 selection conditions based on MARC table
fields. Any way this will not solve our requirement.
Thanks in advance for your answer.
Vignesh M

Hi Bipin,
Yes, that would be an option if we couldnt find a solution for setting a new selection condition in CFM1. Is there a CIF userexit related to sales order? That would be grateful..
Cheers.
Thanks in advance
Vignesh M

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

Condition Value(KONV-KWERT) for Sales Order

Similar Messages

Maybe you are looking for