Replacing Profit Center value while sales order creation process - VA01

Hi,
Profit Center replacement in Tcode VA01 and VA02
I want to replace the profit center value (COBL- PRCTR) in Account assignment TAB in sales order creation time VA01 and VA02 by using custom logic (Line item Material Group and Sales District VBKD-BZIRK).
Can anyone tell me what exit or BADI I can use for this ( I tried some of them and not working properly).
1. In Exit I need to have the value of Sales District VBKD-BZIRK and Line item u2013 Material Value - These 2 field values I need in the exit.
Thanks in advance.
Rajesh.

What do you mean this is not correct user exit. That is an include and there are user exits within that include.
Have you tried save document prepare? If yes, what have you done?
Don't just blindly say 'that is not correct' or don't expect someone code for you. You better try in different way and learn how to do it. I just got it worked in my system just in 5 minutes in debug.
You are not going to change COBL-PRCTR but you should change XVBAP-PRCTR.
put a break point in userexit_save_document_prepare in include MV45AFZZ
Loop through XVBAP and change PRCTR as per your logic.... This changed PRCTR carried till end (billing document/accounting document). I can see the profit center document with changed profit center.
Good luck... if that solves. Mark this thread appropriately.
Most importantly, you better close your previous threads if they are answered. if you solved by yourself post the solution so that others can benefit from that.
@moderator, please check this guy posts
Edited by: Sampath Kumar on Apr 28, 2011 1:16 PM

Similar Messages

Profit Center derivation in Sales Order

Dear Gurus
I have a requirement where profit center should be derived in sales order on the combination of customer country and plant.
In standard SAP it can be defaulted at plant level from material master.
How can this be defaulted on Customer country and shipping plant.
Looking for experts opinion.
Regards,
Neeraj Srivastava

Dear Neeraj,
It is possible to achieve this by using Profit Center Substitution in Sales Orders but as per your requirement Customer country is not available in Table fields but wherein Plant is available. Please find the below example process
The profit center is entered in the material master in the Sales: general/plant view.
When sales order is created the profit center in the material master will be populated in the sales order line item profit center field, which is present in the account assignment tab. This is the standard SAP behaviour.
To substitute the profit center, substitution rules have to be created. To define the substitution rules, use transaction 0KEM or the menu path IMG -> Enterprise Controlling -> Profit Center Accounting -> Assignments of Account Assignment Objects to Profit Centers -> Sales Order -> Sales Order Substitutions -> Define Substitution rules. Once in this transaction, click on Substitution icon to create a new substitution rule.
Enter the code say ZZ01 and description of the substitution rule and click on save.
Select the new substitution rule i.e. ZZ01 and click on the Step icon. System will give a pop up window in which the second option (profit center) has to be selected. Press enter or click on the green OK icon.
After pressing enter, another pop up box will be seen. Here, select the first option i.e. constant value and press enter.
You will be taken to the Step 001 - Overview screen. Enter the description for the Step and then click on Pre-requisites on the left side.
In the next screen, double click on EC-PCA: Substitution in Sales Order under List of Structures. In the next screen, select the item based on which the substitution has to be done. For eg: Division in item.
After you double click on Division in item, you will find the Division in item in the box above. After this click on "=" button which is next to the table fields. You will now find "=" next to Division in item in the box above.
Now click on constant button. System will give a pop up box in which enter the division number on which the substitution rule has to be built for eg. Division 10 i.e. whenever the division at item level is equal to 10 the profit center has to be replaced. After entering the value, press enter. After this you will find in the box above Division in itm = '10'.
Click on Substitutions on the left hand side. On the right hand side enter the profit center number which has to be populated (i.e. the profit center that has to be substituted with) in the sales order line item if the pre-requisite is met. Check the check box next to profit center also.
Click on the save icon. System will give a message save and generation successfully completed. The substitution rule is now created.
Now the substitution rule has to be assigned to the relevant controlling area. To do this, use transaction 0KEL or menu path IMG -> Enterprise Controlling -> Profit Center Accounting -> Assignments of Account Assignment Objects to Profit Centers -> Sales Order -> Sales Order Substitutions -> Assign Substitution Rules. To assign the substitution rule to the controlling area click on new entries and enter the controlling area, substitution rule and active status. Appropriate active status can be given as per requirement for eg: 3.
When the sales order is created, you can observe that the profit center for the line item is 'YYYY' because the pre-requisite is met i.e. the item division of the material in the line item is 10. This means even though in the material master the profit center is 'XXXX', it has been substituted by 'YYYY' based on the substitution rule logic

How to Overrride ATP values during sales order creation

Hi all,
How i override ATP values during sales order creation.
The scenario is that we need to migrate open orders from an existing legacy system to SAP.
While migrating these orders, we need to make sure that dates on the schdule lines are same as they are in the old system. Hence we need to override ATP.
Any suggestion welcome..
Regards,

Hi Kantur Shekar madhuri,
Would you confirm the whether in your schedule line category is activated for "Product Allocation" or not.
if not please activate and re run your scenario.
Regards
Arun

Profit center derivation in sales order with New GL

Dear Gurus,
We are using the New GL, so EC-PCA is not activated.
We would like to set-up a substitution rule in order to derive the profit center in the sales order and customer invoice (we don't want the profit center to always be derived from the costing view of the material master data).
I created a substitution rule with transaction 0KEM and assigned it to the controlling area with active status"3" (Other transactions + cross-company (orders + billing doc.)).
Unfortunately, it doesn't seem to be called when I create a sales order.
Can you please confirm gthat 0KEM is the transaction to use even when we use New GL without EC-PCA?
Where should I put a breakpoint in order to trace the call to the substitution rule?
Thanks a lot in advance for your help.
Regards,
Simo

Dear Gurus,
We are using the New GL, so EC-PCA is not activated.
We would like to set-up a substitution rule in order to derive the profit center in the sales order and customer invoice (we don't want the profit center to always be derived from the costing view of the material master data).
I created a substitution rule with transaction 0KEM and assigned it to the controlling area with active status"3" (Other transactions + cross-company (orders + billing doc.)).
Unfortunately, it doesn't seem to be called when I create a sales order.
Can you please confirm gthat 0KEM is the transaction to use even when we use New GL without EC-PCA?
Where should I put a breakpoint in order to trace the call to the substitution rule?
Thanks a lot in advance for your help.
Regards,
Simo

How to make a field profit center mandatory in sales order?

Dear GURUS,
Please help in getting answer for following question.
How to make a field profit center mandatory in sales order?
With Regards
Sandeep D.

Hi,
There are 2 ways to make profit center mandatory
1.Transaction Variant
2.Incompletion procedure
1.Transaction Variant
Step 1:Goto Tcode shd0 and input transaction as va01 and give name of transaction variant as ( example. zva01 ) and click on create or F5
Step 2.Then it takes you to sales order screen.Just click on enter untill you see profit center field.
Step 3.check the box required against profit center.
Step 4.click on save ( under a package name or as local object ) and exit
Step 5.Assign transaction variant to your sales order type through tcode v0v8.
2.Incompletion Procedure
You can add the field table-vbap,field- prctr,status-04,check-warning to your existing incompletion procedure Tcode- ova2 assigned to your order type in tcode vov8 and check the box - incomplete messeges for your order type through tcode vov8.
If incompletion procedure is not assigned to your order type than you have to create a new incompletion procedure and assign it to order type.

How user exit is used to populate the Profit center field in Sales order?

Hi All,
Please let me know :
How the user exit is used to populate the Profit center field in the Sales order?
Please gurus answer as quickly as possible as I require this urgently.

Hi,
To derive the correct profit center in the Sales Order, you customize in 0KEM.
Trust this helps much and do encourage our efforts!
Cheers!

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

Profit center substitution in Sales Order item level

Dear all,
In Our senario for Sales Order creation time at item level that is material level sale B tab user specified Berth no: in Pricing group field ( KONDA), Based on the Berth no, concern profit center derived from subtitution rule .That purpose I tried Profit center substitution in that substitution,SAP has given PCB SUB structure in that structure main field has given but KONDA field not available, so please guide me how I update that KONDA field to that stucture (PCB SUB) in Profit center substitution area with ABAPER or
I have developed a abap enhancement specifing berth no and profit center assignment and excuting the enhancement in sales order exit. Is there any problem for SD process, Our SD consultant using the sales order user exit for other purpose. He is not allowing to use that exit to execute the zdevelopment
Please suggest me How I update that field into that PCB SUB structure for creation profit center substitution or
can I use zdevelopment through sales order user exit . without affeting the SD process.

Hi
I have the issue like..
1. For each line item of the sales order check, whether the profit center is filled or not, if it is not filled then determine the profit center and populate.
2. If material of the line item is "sub component code" of a material that is "Offering component code", then compare the profit centers of line item with the profit center maintained for the material that is offering component code. If the profit centers are different, replace the sales order line item profit center with the profit center of the offering component code material.
3. Above activities should happen when the sales order is saved.
can somebody tell me which user exit ?? where coding can be dine.

Condition types in Sales order creation process

Hi Friends...
While creating the sales order with BAPI,
What is the condition type i have to pass for pricing procedure...
There many condition types for my pricing procedure, which one o have to select...
Some of them are mannual, and other reuired, which one I have to pass?
I want the information related to this condition types.., as here no SD consultant availble for me.
Sales order creation, Line item error
Thanks,
Naveen.I

Hi Friends...
Please let me know is it mandatory to give condtion type while creating the sales order...?
I am using BAPI_SALESORDER_CREATEFROMDAT2 to create my sales order...
http://www.sap-img.com/abap/bapi-salesorder-createfromdat2.htm
Thanks,
Naveen.I

Sales Order Creation Process.....!!

All,
I have been trying to call "BAPI_BUSPROCESSND_CREATEMULTI" remotely (from .Net environment with SAP .Net Connector ). I understand this is the FM, which is being called from most of other important FM, like BAPI_ACTIVITYCRM_CREATEMULTI or from Sale Order creation BAPI.
Anyway the issue I am facing is that, I have to call "BAPI_BUSPROCESSND_PROCSETTINGS" before calling "BAPI_BUSPROCESSND_CREATEMULTI" to persist the data in Data base tables (even if I am using Transaction Commit).
While calling these FMs remotely, if I call "BAPI_BUSPROCESSND_PROCSETTINGS" and then "BAPI_BUSPROCESSND_CREATEMULTI", it does not work. But If make a wrapper BAPI in CRM with call to "BAPI_BUSPROCESSND_PROCSETTINGS" and then to "BAPI_BUSPROCESSND_CREATEMULTI" within the same LUW, it works.
Now my problem is that I want to use Std BAPIs only (like "BAPI_BUSPROCESSND_CREATEMULTI") and don't want to use any wrapper BAPI..
Anybody could guide me how to surmount the issue I am facing..?Also if somebody knows what this "BAPI_BUSPROCESSND_PROCSETTINGS" is suppose to do?
Thanking all in advance....

I had faced the similar issue while calling the RFC's exists remotely.
I was calling couple of BAPI's in the same session and failing to commit the work in the same LUW.
I have resolved it by calling BAPI_TRANSACTION_COMMIT sequentially in the same LUW.Try to do this.
Do you mention the 'DESTINATION' parameter to the BAPI's ?
And using wrapper RFC's is also recommended.
Thanks,
Thirumala.

Characteristics Value screen suppress while Sales Order creation

Hi Experts,
In Super BOM of header item, we have around 50 materials as Configurable components. Now when user create Sales Order, system first shows Value Assignment Screen for all configurable components. So here user intervention is more.
Requirement is initially system should not show value assignment screen. It should be called only on user's request.
Thanks & Regards,
Vishal Gupta

Hi,
If u have to display all 100 records in table as value help..
n no input field is mandatory thn go for EVS...
which u can excecute on WDinit();
Regards
Khushboo

Profit Center Feild In Sales Order Line item

How can i make the Feild Profit Center in the line item level of the sales order to mandatory?
Please help me regardign this

Hi,
Create a Transaction Variant (T-Code SHD0) and make the field (COBL-PRCTR) mandatory and assign the variant to the order type.

How to update VBFA while sales order creation using BAPI

Hi,
I am trying to create sales orders for each schedule line items while inquiry creation.
This I have done in the user exit in the VA11 program MV45AFF using BAPI "BAPI_SALESORDER_CREATEFROMDAT2".
along with the Inquiry, Sales orders are also getting created. But I am facing 2 problems.
1) BAPI is not returning the sales order number to the program but when checked from SE37 it is returning the sales order
number.
2) It is not updating the VBFA (SD flow) table.
Regards,
Krishna.

Hello,
1) BAPI is not returning the sales order number to the program but when checked from SE37 it is returning the sales order
number.
- are you passing simulation parameter (TESTRUN) as 'X'
2) It is not updating the VBFA (SD flow) table.
- Please use BAPI_SALESDOCUMENT_COPY for copying and updating VBFA table
Thanks
Krish

Profit center derivation from sales order line item - R/3 4.7

Hi,my scenario is below
FI document generated from billing is as
DR:GL1 - its not customer AR,because i post amount to one GL instead customer (profit center is dummy)
CR:GL2 (profit center is correct)
i can see profit center in sales order line item and billing line item,why that profit center not copy to GL1?can someone advise,thanks
Best regards
renhua

Hi phaneendra Reddy ,
The substitution rule is to determine profit center in sales order line item,not for FI document.right?
because i can see correct profit center in sales order.
i know if i post debit site to customer AR,will execute a periodic run to transfer AR to profit center,but now i post debit site to a GL,dont know how to get profit center

COPA error while Sales order creation

Hi,
We are trying to create Sales order and getting error as below;
Inconsistency between a document field and the prof. segment number
Message no. KE396
Diagnosis
A line item was assigned to a profitability segment (number 046xxxxxx) which has the value 0000005xxx for characteristic Customer. The original document (FI document, sales order, internal order, etc.), however, contains Txxxx in this field. It is therefore inconsistent with the profitability segment found.
Can anybody please help me to resolve this?
Thanks,
Niki Shah.

What is the release you are working on? If it were < 4.6A, and you are trying to create an order with refenrence, thenit could be a program error as fixed by note 171064.
Also refer to this [thread|Error KE 396 in sales order;
You may need to fix a program error or add some coding.

Replacing Profit Center value while sales order creation process - VA01

Similar Messages

Maybe you are looking for