Steps for sales order to MRP Run

Dear all,
Could you please explain what are the steps to process after creating sale order to run MRP and delivery?
Regards
Rajasekaran

Hi Rajaseshekhar,
Following will be detailed end-to-end process steps.
                 Create Sales Order Entering Finished Goods Material
                 Master
Auto Generate Alert(E-mail) to Production Planner
                Create ‘Order BOM’ by Copying Finished Goods BOM (Sales
                 Order Item). Amend by deleting/adding Items in Order BOM at all levels
Auto Generate Alert(E-mail) to Product Cost Controller
Recalculate 'Sales Order Costing' to reflect changes to ‘Order BOM’
Auto Generate Alert(E-mail) to Production
Run Sales Order MRP
Convert Planned Order to Production Order
Capacity Leveling
Release Production Order
Pick Components (Picking List)
Confirm Assembly Activities
Post Goods Receipt (Production Order)
Delivery Processing for Sales Order
Create Invoice
Hope ite helps,
Jatin

Similar Messages

Sales order to MRP Run

Hi friends
How to configure MRP run for sales orders.
Thanks in Advance
Rheya

Hi
In order configure MRP for sales orders, check on Transfer of Reqirments on the net or check for the same in Gylence book for Sales and distribution
Few settings for the same are as follows
In t code OVZI
img-sd-basic functions-availablity check and transfer of requirements-transfer of requirements--determination of requirements types using transaction
In this img activity we assign requirement type to the combination of item category and MRP type
I hope this is what you are looking for
In t code OVZI if you go the details you should give the source as 1
Then only it will pick up
This is the pick up strategy
In t code OVZI requirements types are assigned to item category and mrp types
In t code OVZH requirements types are assigned to requirement class
In OVZG we define the controls for requirement class

Sales order with MRP run but no need of sales order stock while PGI

Dear Gurus,
We have scenario in company that we want to run MRP for sales order & generate requirements. But while doing post goods issue for same sales order, sales order stock need not be present.
Please tell which planning strategy, strategy group or else should be used here.
Thanks in Advance !!
Thanks,
Vishwas

Hi,
Please configure in the following manner..
create a strategy group say Z9..in this maintain main strategy as 20 and alternate strategy as 10... Now assign this strategy group to material in material master in MRP3 View..
Now create sales order say A and run MRP with MD50..after completion of production you will get Sales order stock.. now convert this sales order stock unrestricted use stock..
Now before you are doing PGI for sales order A... go to sales order change VA02 and change the requirement type to KSL from KE and then system will all you to do PGI with unrestricted use stock...
Thanks
Kumar

Process order required for each sales order without mrp run

Hi, it is mto scenario. wants system to create a process order for each sales order without running mrp. please advise is it possible? if possible please guide what settings need to be done. Thabk you.

HI
You can create production order with reference to sales order using t code CO08.
Check and revert
Regards
Anupam Sharma

Sales order while MRP run

Hello friends;
My requirement is such that when i run mrp in MD02, system should not consider those sales order that are planned in previous MRP run. System should consider new sales orders that are created after MRP run.
Waiting for reply.
Thanks.

Hi,
One solution is go for individual Sales Order/Line Item MRP run using T.code MD50.
But I can't understand problem with use of MD02.If Receipt element(Plan order)is there which contains the Account Assignment of that Sales Order line Item then I don't think system will replan for same Sales Order Line item.
Regards,
Dhaval

MRP Type V1 does not consider Ext. req. Sales Order after MRP run

Hi Buddies
My client wants to use MRP Type V1 which should consider re-order point as well as external requirement (i.e. Sales Order) for net requirement calculation.However when i tried using V1 in material master and ran MD03 it only considered re-order point and ignored Sales Order.Sales Order didnt even reflect in MD04.Moreover in OMDQ for V1 under additional ext req there is no Sales Order for selection.
Please reply how i can have ext req sales order for MRP Type V1.
Regards,
Sachin Narvekar

Hi
MRP Type V1 creats the requirement when the need exceeds the Reorder Point, where as the MRP type VB creats the requirement when the stock qty goes below the reorder point.
Regards

Acknowledgement of Sales order numbertfor MRP run To PP from SD

How PP will come to know about sales order number acknowledgement which created by SD in MTO scenario.
what is standard solution for it.
thanks!!!

Winni,
My first answer would be to discontinue the use of these dupe orders. I will assume that you have already explored and rejected this solution.
MRP gets SD quantity and Date info via 'Transfer of requirements'. Depending on how your SD system is set up, you transfer requirements at the Item level and/or at the Schedule level (IMG>SD>Basic Functions>Availability check and transfer of requrements>Transfer of requirements).
It is possible to define your SD Items such that they automatically determine a requirements class that does NOT transfer requirements to MRP. Likewise you can define a Schedule line category that does not transfer any schedule line requirements to MRP (IMG>SD>Basic Functions>Availability check and transfer of requrements>Transfer of requriements>Define procedure for each Schedule Line category).
Any changes you make must be consistant with all of the existing SD Doc types, SD Item Categories, and SD Schedule line categories, as well as your existing company policies and procedures. I couldn't possibly make any recommendation without fully auditing your system, and fully understanding all of your business requirements..
I suggest you get your local SD functional expert to work with you to configure your system to meet your
needs.
Rgds,
DB49

Steps for Sales order creation via IDOC

Hi,
I am getting a file on the application server ,which is a purchase order IDoc outbound from another SAP system. I need to use this file to create a sales order through an IDOC in my SAP system. What are the various settings and steps need to be undertaken to achieve this?
Regards
Nishant

Nishant,
This is NOT the way IDOCS are to be used. When you want to communicate between two SAP systems, you recieve a info from a middleware you use IDOCS.
Here if you want you can read the data and call the concerened BAPI, to create the Sales order.
regards,
Ravi
Note : Please mark the helpful answers

Using MD50 to run MRP for Sale Order

Dear all,
I have some problem when using MD50 with Mill Product Industry.
When SAP system not activate Mill Product yet. I used transaction code MD50 to run MRP for Sale Order, the system have generated planned order for multilevel. But when SAP system have activated Mill Product, I used transaction code MD50 to run MRP for Sale Order, the system only generate planned order for single level. I think that we have to configure something based on Mill Product Industry. So can you help me for this
Thanks, Regards

Hi,
Check with following links which may help you resolve your issue :
http://www.sap.com/sme/whysap/industries/millproducts/index.epx
http://help.sap.com/saphelp_di471/helpdata/en/4e/1796374b088e5ce10000009b38f8cf/frameset.htm
http://help.sap.com/content/documentation/industry/docu_is_mill.htm
Regards,
Tejas

MRP-Delivery Schedule for Sales order is not updating in Production order

Dear Experts,
I have created Sales order and maintained delivery scheduling, Then Run MRP through MD50,
We received Planned order then through this we have converted to Prodcution order.
When we observe the delivery schedule for sales order under assignment Tab in Produciton order which is showing zero instead showing line item of Delivery schedule.
I am able to see Sales order and Line item but i am not abel to get any delivery schedule line item.
Please suggest where settings are missing.
Thanks in advance
Regards
Don

Dear Experts,
Please provide me solution.
after Running MD50 transaction against Sales order.
If I maintained different Scheduling Line Item for First Line item of Sales order.
The Respective Scheduling Lines should update against Each Production order which has converted from Planned order.
Thanks in advance.
Regards
DON

Run Sales order wise MRP - AFS material

Dear Experts,
Here my client asking to run the MRP for sales order wise. recently we did the AFS implementation for one of our client. there is an common T-code for MRP run, for AFS material is /AFS/MD02 . they are using material based BOM ( Bill of material). so there might be common material for different sales order i.e if am using material XXXX for Sales order 500 mean , same material will present in Sales order 510 too. current system
( T-code /AFS/MD02) will run MRP of material XXXX Both 500,510 sales order but my requirement is i need to restrict to single sales order.
any one guide me to resolve my requirements.
Thanks in advance...
Regards,
Thangam.P

Dear Venkat,
You are right MD50 does not support AFS material.
Please Try running : /AFS/MD02.
Also Check SAP Note: Note 981747 - FAQ - AFS Production Planning
Hope it will help you.
Regards,
Alok Tiwari

Execute MRP for Sales Order with selected Warehouse

Hi Experts,
When we execute MRP Scenario which include Sales Order. Can MRP only include Sales Order by Warehouse?
For example:
1) We include existing stock for Warehouse-A in MRP Scenario.
2) We include Sales Order in MRP Scenario.
3) We have two Sales Order created, 1st SO is taking from Warehouse-A; 2nd SO is taking from Warehouse-B.
4) I notice that both Sales Order Qty will appear in MRP simulation.
Is there any place to configure to resolve this problem?
Thanks.
Regards,
Lay Chin

Hi Lay Chin,
By the current B1 design, MRP is only working on the item level. That means it consider all on hands in regardless of warehouses. It is not configurable to warehouse level.
Thanks,
Gordon

Invoiced blocked for sales order (configurable material external procurement )

Hello Expert
Configurable material external procurement
Invoiced blocked because ,"Error reading the material cost estimate for sales order "75501"
Message no. KE292
Diagnosis
In Profitability Analysis (CO-PA), the system tried to valuate item
000010 of sales order 75501 by reading the corresponding product cost
estimate.
However, no product cost estimate could be found for this sales order
item.
The system accessed product costing for product 10820 using costing
key 002 as defined in the
CO-PA Customizing
settings.
System Response
The system cannot process the document any further.
Procedure
Check your Customizing settings.
Note:We can't run cost estimate and releasing it because it's a configurable material but external procurement. We place a purchse order based on configurable sales orser
Thanks
Parves

Hello Declan,
Thanks for your reply. Could you please give me the steps for Maintain the
sales order cost estimate?
Requirement: Customer service receive order with variant configuration product,
then MRP Crete PeReq, convert PO and
send to supplier .Supplier configure the product and direct delivery to
customer. Supplier sends an invoice to us. Then we send invoice to our customer
Thanks
Parves

SAP Mobile Sales 2.0 delta load issue for Sales Orders

Hello,
we have used Mobile Sales 2.0 with a Windows app for a while now. Our current issue is that sales reps won't see any historical sales order data on their devices.
Background
Due customer requirements, we need to make small changes to customer master data attributes and reload all customers from ERP to CRM. Then we ran delta loads (MAS_PARTNER followed by all other objects) to DOE, in which virtually all 5000+ customer accounts were compared. The delta load ran for about 3 days (some performance bottleneck we haven't located yet).
During the delta load, data on devices was inconsistent. Accounts were missing and all transaction data disappeared. After the delta loads, all accounts and contacts are OK, save for a few. Data from activities (appointments, tasks) have reappeared, as they should. Only sales orders won't reappear. The sales orders exist in the backend and belong to active accounts and sales reps.
Settings and troubleshooting so far
We don't have any limitations for sales orders in CRM Sales Mobile configuration.
We've run delta loads for all objects in transaction SDOE_LOAD.
MAS_CUSTOMIZATION etc seem fine.
We've re-run initial load for sales orders from CRM.
In the test system, we've even reinitialized the whole CDS database on DOE and on the devices, then re-ran the loads.
Checked steps suggested in discussion
SAP CRM 2.0 initial load issue
Historical sales orders (those created before the master data reload) exist in the backend, but don't show up on the device.
If I change one of those historical sales orders in the backend, it gets sent to the device.
If I create a new sales order in the backend or on the device, it is saved and replicated just fine.
To sum it up, it seems DOE is unable to identify the sales orders relevant for replication.

First Doubt i got clarify by my self as we can go with Unwired Runtime option .
But i still have doubt in :
2. How can i Modifying the Main Menu for iOS.
i am able to customize the same for windows using files SybaseCRM.Configuration.xml file.
Same how can i do for iphone/ipad.

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

Steps for sales order to MRP Run

Similar Messages

Maybe you are looking for