Enhancement for Sales process in FMCG industry

Dear Experts,
I have a requirement for Cross Selling at my client. I have seen several posts in SDN but I have not found the exact solution for my requirement. Kindly suggest as per my requirement.
The requirement is as follows:
My client sells Materials A, B and C. All these 3 materials are individual finished goods that can be sold independantly. Now there is a scheme in the company that if a person purchases 10 quantity of material A, then 2quantities of material B and 1 Quantity of material C also goes freely along with material A. and if he purchases 20quantity of material A then 5Quantity of material B and 3 Quantity of material C is given freely along with material A in the sales order. This is the requirement.
For this I have tried to use Cross-Selling Concept. I was able to configure for cross selling and made the item category as not relevant for pricing. The most important criterion is that the client wants the quantity to come automatically in the sales order. They dont want to enter the free materials quantity manually. So can you kindly suggest me on how to configure this.
Then there is a second requirement. The Base price of Material A has to go to the revenue G/L account while the Base Price of the Free material should go to a different G/L called Schemes Base price G/L. The 100% discount I give on the free material will go to the Business promotion G/L. I can use a separate document type if it was only scheme sales exclusively. But here it is a combination of scheme sales plus ordinary sales. Kindly suggest me on this too.

I have achieved this with the help of my ABAPer by creating a table for this.
I am now closing this thread

Similar Messages

Suggest EnhanceMent For SALES area determination In stock Transfer.

Suggest EnhanceMent For SALES area determination In stock Transfer.
V02V0001 Sales area determination for stock transport order Doesnt Work,

Is user exit required, as the sales area will be different. Incase of Intra company stock transfer the process will be as under:
Create Purchase Order (ME21N)
Create Delivery in background (VL04, VL10a, VL10C, etc)
Change Delivery for picking / packing & PGI (VL02n)
Create Billing Document (VF01)
Assumption: Stock Transfer configuration is in place. Assistance can be taken from SAP Best Practices in help.sap.com
Incase of Inter-company, the process will be as under:
Create Sales Order (VA01)
Create Delivery (VL01N, etc)
Change Delivery (VL02N)
Create Billing Document (VF01)
Assumption: Configuration is in place. Assistance can be taken from SAP Best Practices in help.sap.com
Regards,
Rajesh Banka

Need information on BAPI for Sales Process ?

Hello SAP folks,
I am currently involved in Consumer Portal integration with SAP System. I need information about the right kind of BAPI that would help me to enter and retrieve data from SAP database. I have noted down following funtionality in Sales And Distribution areas where i require a BAPI :
1. Account Management -- > There are concept of Sales rep, Dealer on the consumer Portal. My question is -- > Could anyone suggest some BAPI for creation of User ID for Sales rep and Dealer as well i need information on the BAPI which would also help me displaying the data from SAP database. As far i know, in Customer Master record, we maintain Contact person and Buiness Partners. So how to take up these development into consideration ???
2. Mulitple Credit Card Management --> Please suggest the BAPI for meeting this functionality at Sales order level.
3. Customer Inclusion/Exclusion --> Here the basic need is exclude certain customer from availabling some product. Please suggest the BAPI for this operation.
Regards,
Sarthak

Dear Sarthak M,
Assume you have gone through the transaction BAPI,
where you can find all relevant BAPI's .
select the relevant text such as "sales orders" - from the right side of the screen - check "Tools" tab,where you will find "Create BAPI list", click to search for the Function moduels.

Enhancement for Sales Order

In standard SAP sales order there is no field to refer the custom field Z_ID which is reference of internal orders. if the sales order has any free goods items then a check should be made against relevant item category.
If free goods are there ZID should be maintained in the sales order if not the end user should be forced to enter the mandatory Z_ID before saving the order.
Free goods items can be known by item category u2018ZAFGu2019 from VBAP
I need to add the custom field Z_ID to vbap table and put logic in exit to handle and show an error message in va01 screen saying "Z_ID is missing in line Item XXX"
User exit : SAVE_DOCUMENT_PREPARE
Please let me know how can i add custom field to additional data B tab in sales order.Thanks.
Sanjeev
Edited by: sanjeev.s on Jun 25, 2010 1:41 PM

Hi Rajendra,
I agree it asks for an additional field in 8459 screen, but is there any option we can implement with out using access key.
Regards,
Sanjeev

Siebel 8 module enhancement for sales

Hi
We are planning for upgrading to Siebel 8 crm system. We have already some reports in cognos based upon different modules in Siebel.
I want to know the new features/enhancements in Siebel 8 in existing modules so that the corresponding reports can be upgraded in incorporate the new features.
In case some database level changes are there (new columns, new modelling relationships) , pls let me know that also since the reports will be changed.
Regards

This forum is for Siebel CRM On Demand and not Siebel 8. Please post this question on the correct forum.

Customer master enhancement for sales

Hi
I am getting the customers data from 0CUSTOMER_ATTR , I have all the fields what I need , except Sales Organization which is from KNVV...and Payment Block ZAHLS which is from KNB1...So can any one tell me do I need to enhance 0CUSTOMER_ATTR or can I get this 2 fields value from any of the other Object as read from master data.?
thanks?

Hi,
KNVV is reflecting customer infomation at sales organization level.
A customer doesn't belong to a sales organization in general. Except special customizing, a customer could have different attribute values in several sales organization. In fact the distribution channel and the division are also part of the key.
The business content IOBj is 0CUST_SALES and can be loaded with 0CUST_SALES_ATTR
The payment block would come from another segment of the customer: the company code data IObj 0CUST_COMPC, DSource CUST_COMPC_ATTR.
hope that helps...
Olivier.

Data source Enhancement for Sales Item

Dear SDN Mates,
We are enhancing the data source 2LIS_11_VAITM, when i try to enchance extraction structure it is not allowing to enhance. Showing a message :"2LIS_11_VAITM does not allow enhancing or append structure"
Mates if you came across these difficulties please let me know and suggest any ideas.
Thanks and Regards
Arun S

Hi,
Have a look at these links:
[SAP BW Data Source Enhancement|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/302d4b15-5847-2a10-93bb-9c45d9f06b16]
[Data Source Enhancement|Data source Enhancement Code Samples;
Hope it helps...
Regards,
Ashish
Edited by: Ashish Tewari on May 11, 2009 12:16 PM

Enhancement for Sales Quotation(SAPMV45A)

Hello,
Please can anyone tell me if the additional data A screen area available in transaction (VA11/21) can be customised.
If yes, What is the screen no.I am unable to find it.
Currently I am using screen no 8309 for additional data B.
There is also screen 8310 available.Where can this screen be used.
Regards
Amruta

I'm also interested in this issue, I quote:
<i>"I would like to know if the additional data tabs can also be included in the bapi BAPI_QUOTATION_CREATEFROMDATA."</i>
Which means, the custom (Z*) fields.
Thanks in advance!
Miroslav.

DRQ: Different default warehouse for Sales,Purchase and Production Process

Hi Experts,
In my recent Implementation Project I realised that there should be provision of capturing and using different default warehouse for Sales,Purchase and Production.
For example in manufacturing company
1. Default ware house for Purchase process should be QC ware house for raw material.
2. Default ware house for Production process should be RM ware house for raw material (components).
3. Default ware house for Production process should be QC ware house for Finished Good (Parent Item).
4. Default ware house for Sales process should be FG ware house for Finished Good (Parent Item).
I hope the idea is clear, I am looking for 3 different set as default warehouse for each item in Item master Inventory tab.
Internally when a user create a document than default warehouse is to be picked up from this setting !
Best Regards,
Samir Gandhi

Hi !
I guess the indicator "Exclusive" in the accessess of the access sequence can meet the requirement if I have note misunderstood the issue.
Press : F1 help on Exclusive Indicator -
Indicator: Exclusive condition access
Controls whether the system stops searching for a record after the first successful access for a condition type within an access sequence.
Thanks & Regards

Enhancement for bin to bin stock transfer

hi,
when i am using stock transfer bin to bin using LT01 transaction, an information message have to raise when same material/batch if destination bin already having.........
i already searched enhancement for above process "MWMTO001" i am correct or not?
Thanks
Muthuraman.D

Yes, that's correct. You are using the right enhancement.
It has the LTAK and LTAP tables which is the transfer order tables. This function will trigger during the TO creation.

Sales process in crm

Hi Can any one tel abt crm sales process.
1. once so created in crm how it will replicate to the r/3 and wht is process is gng on in r/3
2. tel the contracts scenario in crm
Help me know this scenarios.
Edited by: gs.kumar on Jun 9, 2010 7:27 AM

HI,
The best way to know the processes you mentioned is through help.sap
Follow the link:
For sales process:http://help.sap.com/saphelp_crmscen70/helpdata/en/3e/24b225d18147fd820421368dd73e62/frameset.htm
For contract process: http://help.sap.com/saphelp_crmscen70/helpdata/en/3b/eb8b523e50434cab89c71d19169711/frameset.htm
Regards,
PP

CRM winclient sales process probelm

Hello Experts,
I am working on CIC winclient sales process.
I have created Quote and follwup order in winclient.
But when I open the Quote in GUI(CRMD_order) transaction it is displaying with multiple follwup Quotes along with my sales order.
When i go and see the document flow ,
From Quote to order it is showing "Next Document,"
But Quote to Quote it is showing "participent communication process"
Please let me know why the system is behaving like this.
Thanks

HI,
The best way to know the processes you mentioned is through help.sap
Follow the link:
For sales process:http://help.sap.com/saphelp_crmscen70/helpdata/en/3e/24b225d18147fd820421368dd73e62/frameset.htm
For contract process: http://help.sap.com/saphelp_crmscen70/helpdata/en/3b/eb8b523e50434cab89c71d19169711/frameset.htm
Regards,
PP

Post order processing for sales document is not yet complete

hi,
sap gurus,
i am facing the error while saving the sales order and this ticket is unique and it is saying that
"post order processing for sales document is not yet complete".
please help me in this regard.
and it is blocking the order for further processing.
regards,
balajit

I dont think this is a standard error message. Some exit is applied for sale order to meet some requirements. You need to check with your ABAPer.
In fact, you can conclude yourself based on the error message number. If it starts with Z, then the above holds good.
thanks
G. Lakshmipathi

Credit Memo Request for intercompany sales process

Hi Experts
I try to find SAP notes regardsing the credit memo request for intercompany related issue but I can
not find any nates. The customer return the goods with 2 different
scenario :-
-Return with credit
-Return with replacement.
Can anybody explain how this 2 scenario perform in the SAP
intercompany sales process. Appreciate for your help. Thanks in advance.
Regards,
Jennie Tan

Already answered
Enter IG (internal credit memo) as the billing type for intercompany
billing for order type RE.
Cust-Sales/distrib-Transactions-Billing-Intercompany billing-Order types
Intercompany billing always refers to a delivery
Processing flow will be:
1. Create returns request invoice receipt (with or w/out reference)
2. Create returns delivery and goods receipt
3. Create credit memo invoice receipt for customer for 1.
4. Create internal credit memo for 2.
Therefore you must make the following entries in the document flow
for billing documents:
Target BillType        DlvType              ItemCat
a)    IG                  LR
b)    IG                  LR                    REN
Parameters for entries:
For a) Copying requirement: 14 Dlv.-rel.header IV
      Copy item no.: x (Check and decide yourself)
For b)Copying requirement: 15 Dlv.rel. item IV
      Data VBRK/VBRP      : 1 Inv.split (sample)
      Billing quantity    : B
      Qty/itm val.pos/neg : +
      Pricing type        : G
Also, refer following SAP Notes
13160 - Returns with intercompany billing
24756 - Credit memo requests with inter-company billing
652007 - Reporting internal credit memos on arrival side
11980 - Intercompany billing with order-related billing document
164074 - Problems for internal invoices on returns
Thanks & Regards
JP

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

Enhancement for Sales process in FMCG industry

Similar Messages

Maybe you are looking for