Business Area in header level of sales order

hi Gurus
i have one query that the szystem dont take the business area automaically(default) on header level
whts the setting oftha
i have already assigned the business are4 to Sales Are & Plant & division too
and taken the rul 3 for that.................
plz give me the solution for thi
Suitable answers will be rewarded
Regard
Amol Gawai

Hi,
I think since plant and division both are derived from material master into the sales order, and your business area is assigned to your plant and division, then in that case it wont default from the header.
Also if you assign it to your sales area, it will still take at item level.
Hope this helps.
Reward if helpful.
Regards
Ravi

Similar Messages

Impact Analysis: Business Area, Profit Center changed for Sales Order type

Hi All,
Can you please let me know the impact of changing the Business Area and Profit Center for Sales Order Document types.
Scenario:
Let's say that sales document type ZOR has been used for sometime. On this document x number of sales orders have been raised, delivered and invoiced over the years.
Now, if you change the Business Area and Profit Center what would be the business impact.
thanks,

Hi,
First of all itu2019s not a good business practice to change the Business area and Profit Centre.
However if at all l you change the Business area and Profit centre the following is the impact::
Business Area: effects the sales order in accounts assignment at Header level.
Profit centre: effects the accounting part at Item level
Overall in MIS reporting w.r.t Profit and Business Analysis in Finance will be affected.
Thanks and regards
DSR

Rounding at Header Level in Sales order

Hi all SD Expert,
Question:
Can rounding mechanism be applied at Header level in Sales Order?
Summary:
The government of Malaysia have implemented the rounding mechanism to the nearest multiple of 5 cents over the counter transaction. This mechanism shall apply to the total amount of a bill.
Example:
- $1.01 or $1.02 will be rounded down to $1.00
- $1.03 or $1.04 will be rounded up to $1.05
- $1.06 or $1.07 will be rounded down to $1.05
- $1.08 or $1.09 will be rounded up to $1.10
refer http://www.bnm.gov.my/index.php?ch=209&pg=657&ac=567 for more info
My Problem:
SAP Note 1165950 suits well enough for 1 item per sales order.
Example:
Total Bill = $1.38 (posted to a dedicated G/L account)
Rounding Adjustment = +0.02 (posted to a dedicated G/L account)
Total customer to pay = $1.40
But, if I have 2 or more item per sales order, my rounding mechanism does not meet the requirement. Example:
Item 1:
Total Bill = $1.38 (posted to a dedicated G/L account)
Rounding Adjustment = +0.02 (posted to a dedicated G/L account)
Total customer to pay = $1.40
Item 2:
Total Bill = $1.38 (posted to a dedicated G/L account)
Rounding Adjustment = +0.02 (posted to a dedicated G/L account)
Total customer to pay = $1.40
Total Item 1 + Item 2 shown in header level = $2.80
In Header Level, the rounding figure shows +0.04 (rounding adjustment item 1 + item 2). I dont want my sales order to round the value at item level.
The correct calculation to suit the regulation is:
Item 1 + Item 2: $1.38 + $1.38 = $2.76
Rounding Adjustment at Header: -0.01
Total customer to pay = $2.75
can someone help me?
TQ
Ezwardi

Dear Tengku
Please try with this.
Go to V/08, for the net value field, maintain Routine 16 in the Alt. Cal. Type. Also add Routine 17 to Netvalue.
As you know Condition types are assigned at each item level. So rounding off is calculated at each item level. But by assigning a tick in the Group Condition while defining Rounding off Condition, you can do rounding off at invoice level. The difference is automatically adjusted at each item.
thanks
G. Lakshmipathi

Change the Payment Method at header level in Sales order document.

Hi Experts,
I have a doubt and a problem; I want to change the Payment Method at the header level however that is not possible never at header level is the same even either I chose other when I was creating the sales order document or I tried to change after that. The system allows changing the Payment Method but when I display the document after that the change is not done always is the same payment method. Maybe it is defined at customer or sales organization level.
At item level it is possible change the payment method with any problem.
Thank you and best regards.

Dear Alberto
Payment Terms can be changed both at header level and at item level in sale order.
thanks
G. Lakshmipathi

Relation between business area and WBS element in sales orders

Hi,
I need to find the business area for WBS element for line items in sales orders.
Which database table can I use for that.
Thanks,
Abhishek

Check these tables PRPS WBS (Work Breakdown Structure) Element Master Data
PRPSS Standard WBS Element (WBS element) - Master Data
Field PGSBR ( Business area for WBS element )
PSPNR (WBS Element)

Deactivation of Pricing Conditions at header level of Sales Order

Hello there,
We have used a routine in pricing procedure (BaseType Routine) to deactivate condition MWST in the MWST condition line in pricing procedure, transaction V/08.
In the routine, We played with the KINAK (set to K )and KOBLI (set to space) flags of structure KOMT1 and XKOMV and delete the MWST entry in the TOBLI table and succeeded to deactivate the MWST at item level of the sales order. (MWST condition appear in the conditions tab at item level as inactive)
We have created a sales order with only one item that has the MWST condition deactivated at item level.
But in the conditions at header level the MWST condition does not appear. Shouldn't the MWST condition appear at header level but deactivated (with a yellow triangle next to MWST)?
If yes is there a flag that we forgot to set?

Hi,
what is the table name you had mentioned
TOBLI is it correct?
Thanks
mano

Pricing Conditions deactivation at header level of Sales Order

Hello there,
We have used a routine in pricing procedure (BaseType Routine) to deactivate condition MWST in the MWST condition line in pricing procedure, transaction V/08.
In the routine, We played with the KINAK (set to K )and KOBLI (set to space) flags of structure KOMT1 and XKOMV and delete the MWST entry in the TOBLI table and succeeded to deactivate the MWST at item level of the sales order. (MWST condition appear in the conditions tab at item level as inactive)
We have created a sales order with only one item that has the MWST condition deactivated at item level.
But in the conditions at header level the MWST condition does not appear. Shouldn't the MWST condition appear at header level but deactivated (with a yellow triangle next to MWST)?
If yes is there a flag that we forgot to set?

Hi experts,
Has anyone done the above mentioned before, please reply...

Profit Center at header level in sales order

Hi Friends,
Is it possible to have profit center entered at header level in a sales order. If yes then where.
Regards,
Wasim.

No, profit center is always assigned at item level.
One of the reason could be, items in a sales order can have different profit centers, hence assigning at header level will impact all the items.
Regards

Partner function in header level of sales order

Hi All,
During the sales order create/change (VA01/va02).
Depending upon the business unit i want to populate partner function.
I have modified the user exit "MV45AFZZ - userexit_save_document_prepare " and userexit_save_document .
i tried both the exit.
During debugging its deleting from the XVBPA table but its not reflecting in the final screen.
in final screen its showing the partner function from master data it is not updating from the exit.
<< Moderator message - Everyone's problem is important >>
Thanks in Advance.
Edited by: Rob Burbank on Nov 11, 2010 3:49 PM

you can populate XVBPA-UPDKZ = 'D' for the row you want to delete from XVBPA.
I Hope it will work for you.
Thanks
Raj

How can we revise the pricing both at header and item level of sales order?

Dear All,
Now there's one issue of the pricing to me. i want to revise the pricing both at header and item level of sales order. but after i finished the cutomize and tested it, it's more different as i thought. i found that the pricing can revise at the one side only,for example, if i revise the pricing at item level and it's grey and can't be revised at the header. on the other hand, it's the same result what's happened at item.
So, in my opinion, we can't revise the pricing both at header and item, right? if not, please give me more advices and teach me how to solve the problem. thanks a lot.

Dear Lakshmipathi,
Thanks a lot for your kindly and useful answer for me and I learn more for the pricing technology.
I didn't notice the way that you reminded ago therefore I also saw the button at the condition tab. And your suggestion makes me know more.
And I had tested the way that you said, I met with a question. Below is my opinion for my testing.
I had created one SO and the pricing was $10, then I revised the pricing from 10 to 15 by VK11. It can't be updated automatically at SO and I must update it manually by clicking the "Update" button. This is OK for my testing, but I have another question to disturb you for the use of "Active" button. When I click the button and nothing is responsed, it's quite different what you said. So, please give more detail for the Active button. Thanks a lot.

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

Billing tab of BP are not populated in the sales order automatically

Hi
Business Partners Billing Tab details like customer pricing procedure, currency, price group, Customer group etc are not populated in the Sales order automatically?
I have checked the pricing procedure determination also.
Thanks

Thanks problem is solved.

Sending Alter Text by mail automaticlly on item level of Sales order.

There is a 'Alter Text ' listed on the tabpage 'Texts' at item level in Sales order.
I want to send content of 'Alter Text ' by mail automaticly as end user change the text .
How to implement this requirement?
Thanks

Hi,
U can add the field in sales order header (Additional Data B tab). pgm name = SAPMV45A screen no: 8309.
Regards
Sathis

Business Content for Product Cost by Sales Order

Hi,
We need to do reporting on costs associated to Sales Orders. The corresponding R/3 Area is "Product Cost by Sales Order" in Cost Object Controlling. We have looked at the standard cube for Cost Object Controlling (0PC_C01) but this cube only contain costs related to manufacturing orders, whereas we need to look at costs associated with sales orders after Result Analysis.
Have you guys any ideas which content that might support this, if any?
Many thanks!
/ David

Hi Christian,
please refer to SAP Note 584791: <a href="https://websmp208.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=0000584791&nlang=E">BW-BCT-CO: Costs not extracted on sales orders</a>.
Unfortunately there's no DataSource providing the data you need for your analysis scenario. A custom development is needed (awful!!)
Note 584791 - BW-BCT-CO: Costs not extracted on sales orders
Symptom
In R/3, costs are posted directly to sales orders. The costs have to be analyzed in the BW system. In the standard system, however, this data is not extracted into the BW system.
Other terms
0CO_OM_OPA_1; 0CO_OM_OPA_6
Solution
1. There are currently no DataSources for costs on sales orders in the standard BW Business Content. Unfortunately, there are currently no resources scheduled for a new development in this area either.
2. Therefore, the DataSources and the Business Content must be created in the customer project within the framework of consulting as a customer solution concerning the generic extraction options of the BW Service APIs or function modules you have programmed yourself for extracting data.
3. Technical background information about costs on sales orders:
The transaction data is available in the following R/3 tables
COSS and COSP - Totals records or COEP - Line items.
This concerns records for the VB* object numbers.
The master data of the sales orders is contained in the VBAK and VBAP tables.
The 0CO_OM_OPA_1 and 0CO_OM_OPA_6 DataSources only extract costs for orders with master data in the AUFK table. These types of requests always have OR* object numbers. Therefore, these DataSources cannot be used for sales orders.
However, you may be able to assign requests from the AUFK table (for example, maintenance orders or production orders) to a sales order through the AUFK-KDAUF table field.

Dump after creating new header text on sales order and invoice.

Hello,
We have created one header text on sales order and the same text for invoices, on VOTXN customizing.
Testing the new text, system let us save the text fine, but later, if we display the text, system give us dump error.
My question is, after transport the customizing to the next environment, is necessary run a standard program. Since VOTXN, we have generated the new access created, but dump appear displaying text header tab.
Any help on this?
Thanks in advance

Hello Customer master table man
1) Did you review the dump analysis- ST22? Do that because the dump amy or may not be related to the Text config changes.
2) You are also mentioning about transporting? Did you already transport and are facing this issue in the target client or is it happening in the source client and you want to avoid it in the target? OSS note 1117467 throws light on transporting issues.
Review the following OSS notes:
548615 - FAQ: Text determination in SD II
548517 - FAQ: Text determination in SD I
1117467 - Text Customizing change not transferred in target system II
970153 - Change to Customizing text not transferred to target system
Hope this helps.

Business Area in header level of sales order

Similar Messages

Maybe you are looking for