BOM related issue-in sales order creation there is info message-

hi all expert,
1)when user create sales order for BOM item.system show
message"Consider delivery unit 6 ZUN in item 000020"
where i can check the setting.
2)
user create one BOM with t code cs01.
mail item is-mm004
subitem is- MM02 and mm03
same sub- item is maintaind two time in one BOM
for example:
main item-mm04
sub-item------MM02 -
5 qty
                  MM02----
1 qty
                  MM03----
10 qty
                  MM03----
2 qty
in this case system is picking first Qty in our example
is 5 for mmo2 material and and for second material MM02
its taking 5 (not 1)
this is user issue what i should sugget to user
please tell me
as per my understanding they should not maintain same
material for two time with different Qty.they can maintain
material MM02- for qty 6(5+1)
please suggest me
regds
alicia

Dear Alica,
Why they are maintaining same material as two sub items then can maintain those as one sub item
So you ask them to maintain like this
MM02--6 qty
MM03--12 qty under MM04. Then try
I hope it will help you
Regards,
Murali.

Similar Messages

Issue in Sale order creation from program

Hi Friends
As per our project requirement we are creating sale order from ABAP Program.
We are adding all the line item values from some table and pushing it into final internal table.
After the loop statement we are adding one more material( Material X) in the final internal table through hard coding.
Its working fine in Dev/QA/SND,but when it comes to production its adding the material(material X) in multiple lines(only in some cases).But as per our logic it should come only once..
we are not able to replicate the same scenario in Dev/QA/SND.
So anybody have an idea about this kind of issue.Kindly let me know.
Thanks in Advance.
Thanks
Gowrishankar

Actually I added like that only.
LOOP AT idoc_data WHERE segnam = c_e1edp19.
          indx = sy-tabix.
        ENDLOOP.
        LOOP AT idoc_data WHERE segnam = c_e1edp01.
          index = sy-tabix.
        ENDLOOP.
        READ TABLE idoc_data INDEX index.
        IF sy-subrc = 0.
          segnum = idoc_data-segnum.
          wa_e1edp01 = idoc_data-sdata.
          n_posex = wa_e1edp01-posex.
          n_posex = n_posex + 10.
          CLEAR: wa_e1edp01.
          wa_e1edp01-posex = n_posex.
          wa_e1edp01-menge = '1'.
          wa_e1edp01-menee = 'EA'.
          idoc_data-sdata = wa_e1edp01.
          indx = indx + 1.
          INSERT idoc_data INDEX indx.
        ENDIF.
        CLEAR: n_posex, n_config_id, n_inst_id.
        READ TABLE idoc_data WITH KEY segnam = c_e1curef
                               psgnum = segnum.
        IF sy-subrc = 0.
          e1curef = idoc_data-sdata.
          n_posex = e1curef-posex.
          n_posex = n_posex + 10.
          e1curef-posex = n_posex.
          n_config_id = e1curef-config_id.
          n_config_id = n_config_id + 1.
          e1curef-config_id = n_config_id.
          n_inst_id = e1curef-inst_id.
          n_inst_id = n_inst_id + 1.
          e1curef-inst_id = n_inst_id.
          idoc_data-sdata = e1curef.
          indx = indx + 1.
          INSERT idoc_data INDEX indx.
        ENDIF.
        idoc_data-segnam = c_e1edp19.
        wa_e1edp19-qualf = '002'.
        wa_e1edp19-idtnr = c_sm.
        idoc_data-sdata = wa_e1edp19.
        indx = indx + 1.
        INSERT idoc_data INDEX indx.
      ENDIF.
    ENDIF.
Its working in DEV/QA/SND part..

Issue in sales order creation configuration.

Hi Friends
I want to create a sale order from IDOC using configurable material.I filled all the required values for that configurable material,But while executing this idoc its creating a sale order for some kind of material, but its not creating for some kind of material.
But if I delete the segment 'E1CUCFG' from idoc table before calling the standard function module IDOC_INPUT_ORDERS its generating the sale order number.
But if I delete that segment, its not activate the config part and not fill all the line items in sale order.
I checked in all the way, but I didnt get any idea.if anybody have an idea about this let me know.
Thanks
Gowrishankar

Hi Vindo,
Thank you for your replay.
There is no Net value column in pricing procedure. Am able to change the Net value in the condtion tab of Item level but the problem is , the change is not reflected in condition tab of sales order header net value.This is creating a problem when we try to post the invoice document .
Cheers,
sravan.
Edited by: Rob Burbank on May 7, 2010 4:30 PM

Issue regarding Sales Order creation using bapi BAPI_salesorder_createfromd

Hi Experts,
Can anyone help me what is the data I'm missing in creating sales order?
I tried to create sales order using BAPI_salesorder_createfromdat2 and I recieve error regarding my creation.
here's the lists of RETURN for the BAPI.
"SALES_HEADER_IN has been processed successfully"
"SALES_ITEM_IN has been processed successfully"
"SALES_CONDITIONS_IN has been processed successfully"
"The sales document is not yet complete: Edit data"
Iam not able to get the message ""The sales document is not yet complete: Edit data"
Please help in this regard.
Regards,
Sakti

This is because you are still missing some segments or data.
Maybe this thread will be helpful:
BAPI_SALESORDER_CREATEFROMDAT2 to replace VA01, KBETR and NETWR
You should also check the documentation from transaction BAPI.

How to fetch post goods issue date and sales order creation date

Hi All,
How to find out the difference between SD Sales Order Item Creation Date and final Post goods issue Date. I would like to know how to fetch those dates and what is the relationship between the tables from which i will get the dates.
Please let me know the solution .
Thanks in advance.

Hi,
Sales order creation date is when u raise a sales order in favor of the customer using VA01.......using ATP logic system purposes the material availability date....
after saving ur sales order...when u raise the Delivery using VL01n w.r.t to OR...than u have to perform picking ....In the picking Tab...specify the amount to be picked than press Post Good Issue....means the goods left the company premises ..
You can the fetch the values using tables- Use T code SE12 or SE16
Vbak-----order header
Vbap-----order item
Vbek-----order schedule line
Likp-----Delivery header
Lips----Delivery item

Dump during sales order creation for a config material (uding order BOM)

Dear all,
I am getting the following error during sales order creation for a configurable material
When I click on 'Engineering' tab in the characteristics value assignment for the parent material i.e. sales order material I get dump with following message,
'Field symbol has not yet been assigned'
Thanks,
Yogesh

Yogesh,
what was the problem ?
Thanks,
Pavan Verma
Edited by: Pavan Verma on May 11, 2010 9:31 AM

BOM business requirement for sales order and PGI

Hi Experts,
Current setting
The BOM structure is A = A1+A2
1) Material A created in MM master item category group = ERLA
2) Sub component material A1 and material A2, MM master item category group = NORM for both component.
3) Maintained in CS01 BOM header is A and items are A1 and A2.
4) Item category in IMG was created and assign item category also created.
    4.1) OR-ERLA-TAQ-TAE
new business requirement as listed below.
5) The material A is alway zero quantity on hand, no goods receipt required with no physical with such material or package at all. (it is dummy material number in SAP).
6) while SO created.
    6.1) Fro material A sales price captured at BOM header level only, NO QTY and COSTshow in the sales order.
     6.2) Material A1 and A2 are actual physical inventory item in the ware house.
     6.3) The sub component of material A1 and A2 is required to captured QTY and COST. NO SALES PRICES NEEDED.
CONCLUSION
HOW to setup/configure such a business scenario?
- Is it logic to configure as OR-ERLA-TAE-TAN that's what i think of?
My problem is how to make the material A is alway ZEROS stock on hand and allow in sales order creation with ZEROS order qty?
MATERIAL                                          QTY                             COST                                  SALES NET VALUE
       A                                                      0                                   0                                              1,500.00
       A1                                                    1                                  100.00                                           0
       A2                                                    1                                    50.00                                           0
Thanks & Regards,
Yong Kok Wah
Edited by: Yong Kok Wah on Jan 27, 2010 11:16 AM

As per your post,
- You are creating Main item which is a dummy material without any physical inventory maintained, but the pricing/billing should be done @ main item level.
- here you are not dispatching main item, but billing should be carried at this level. in such case, I suggest you to go with the new sch.line cat w/o maintaining any mov type to it. & use Zitem category for this main item in VOV7, mark "Order qtty=1" so that min order qtty for this main item should be 1, so that you can calculate price.
- You want to capture Cost of sub items , summation of sub items cost is total cost of main item & Profit will be calculated accordingly.
Sub items, sch.line category should have mov type, item cat should be not relevant for pricing & billing , but relevant for sch.lines. In Copy control from delivery - Billing @ item level, for the main item ,- item category, choose "Cumulate cost", so that cost of the sub items will be cumulated to main item.
eg:
MATERIAL QTY COST SALES NET VALUE
A 0 0 1,500.00
A1 1 100.00 0
A2 1 50.00 0
My problem is how to make the material A is alway ZEROS stock on hand and allow in sales order creation with ZEROS order qty?
To avoid this, mark order qtty=1, in item category for main item, but for the same item, sch.line category should not have mov type. so that there will nt be any PGI document. But PGI should be done for sub items to capture inventory & cost.
Test & revert, if any issues.

Automatic Sales Order Creation from PO in B1

Hi,
I have this scenario. Purchase order is created in SAP B1 (Business One) which triggers automatic Sales Order creation in SAP ECC 6.0.
The requirement:
For the combination of PO number and Sold to party there should be only one sales order created.
The problem:
Sometimes for the same PO duplicate Sales orders(sometimes 3,4) are getting created in ECC.
Possible causes:
Probably no validations in the interface.
Question:
1. First of all, is it an SD issue or PI (process integration) issue.
2. If it is an SD issue, as a functional consultant what / where can we do to prevent this.
Thanks.
Edited by: SAP SD_Newbie on Oct 20, 2011 6:59 PM
Edited by: SAP SD_Newbie on Oct 20, 2011 6:59 PM
How do I move this to "ERP - Sales and Distribution (SD) General", because this question is not just related to "ERP SD Sales" but SD in general. Isn't there an option for the users to a question from one forum to another.

1. First of all, is it an SD issue or PI (process integration) issue.
- May be PI, or SD or both. I am not sure about the integration mechanism/program so I am not able to pinpoint.
2. If it is an SD issue, as a functional consultant what / where can we do to prevent this.
In t.code VOV8, go to the sales document type. Select value A in the field, check Purchase order Number. Then go to t.code OVAH, there make the message number V4 115 as error message. This will not allow the creation of the sales order, if the Purchase order number duplicates. I assume in your process, the purchase order number is populated in the PO number field of the sales order overview screen.
Regards,

How to block material issuing after sales order invoiced?

As the subject mentioned, could be a possible to block material issuing since sales order invoiced, or
in the another words, after the sales order completed?
Or could be a possible to set sales order as closed, and then material issuing related with this sales order are
forbidden?
Thanks in advanced,
Zhou Zhen

Dear Friend
A sales order is created say order no 10000 and for material X say 10 units this order is delivered and PGIed and invoiced and the payment too has come
That means the order 10000 is closed
Case 1
Now an user goes to VA02 t code and put this order no 10000 and changes the material X qty from 10 to 12 and opens up the whole order once again
This can be controlled by using t code OVAH choosing message class the V4 message no 083 and change from warning to error
Case2
But to avoid the user to add material Y to the existing order say 10000 then i think we have to go for user exit
Because the system doesnot even throw a warning message too in case 2 (according to my knowledge) and allows another line item to be added in the same order
But you can test it if it throws any warning message we can try to convert that error
But in case 2 it is not happening(even warning is not there)
Regards
Raja

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

User Exit during Sales Order Creation - New Line Item needed

I have a situation during the process of sales order creation. If a Material in a line item has say 27 EA and the Base Unit is EA. But the Sales Unit is CSE. Then whenever the user enters 27 EA and presses enter he should get two line items.
The first line item needs to convert to maximum number of CSE posible and the rest will be the second line item with the remaining EA. The order isn't important but that is what is needed. Question is how do I approach this problem and code my user exit accordingly and where do I code it.
I was looking at SAPMV45A and saw the program MV45AIZZ which is meant as a user exit for any PAI event handling. If anybody has encountered this kind of requirement can you please share your view on this.
I will definitely reward points for useful answers.
Clark

Hello Mahendra
The requirement is as follows :
PART 1:
Sales Order Enter:
1.     When a line item is entered on a sales order (VA01 or VA02), at enter, check the sales unit of measure (VBAP-VRKME).
     Do not check line items where item category (VBAP-PSTYV) = TANN, TAPS or ZTAP. TANN are free goods that should not be considered for consolidation. TAPS & ZTAP are lower level materials as a result of product selection. They will be attached to a higher-level material with an item category of TAX, which is relevant for consolidation.
     Do not check items where VRKME <> EA
2.     If VRKME = EA, go to MARM for MATNR.
3.     Go to record where alternate unit of measure (MEINH) = CSE, get the value from the numerator field (UMREZ).
4.     Divide the order quantity (VBEP-WMENG) by UMREZ.
5.     If the result is greater than 1.0, the customer has ordered more than one case and a new line item needs to be added to the sales order for the case quantity.
6.     Add a new line to VBAP for the same material with the case quantity. If not a whole value, the remainder of eaches (bottles) should update the qty on the first item on VBAP.
     Part 1 is relevant for order types ZCA, ZOR, ZSO, RE, ZSM
PART 2:
Batch Job to run prior to the Delivery Due List:
1.     Read VBUK for Delivery Status (LFSTK) = A (delivery not processed). Get all of the document numbers (VBELN).
2.     Go to VBEP for those document numbers to get the goods issue date for the order. There will be many records in VBEP for the same sales order. Look at all orders with a goods issue date (WADAT) of next day.
3.     Go to VBAK for those document numbers to see if there are multiple sales orders for the same Sold To party (KUNNR).
4.     For customers who have more than one order in VBAK, search all line items (for all orders). If there are no duplicate materials across sales orders, do nothing.
     Do not check line items where item category (VBAP-PSTYV) = TANN, TAPS or ZTAP. TANN are free goods that should not be considered for consolidation. TAPS & ZTAP are lower level materials as a result of product selection. They will be attached to a higher-level material with an item category of TAX, which is relevant for consolidation.
     Do not check line items where reason for rejection (VBAP-ABGRU) is not blank
5.     If there are duplicate materials, go through the same logic as in part 1. If the quantity across the sales orders adds up to greater than one case, add the appropriate quantity to a new line item on the first sales order.   If there is a remainder qty, update the line item on the first sales order with this qty. In this case, the quantities on the second sales order needs to be closed out with a reason for rejection code of 50, Line Item Consolidation. If there is no remainder, update the qty on this item directly.
     Part 2 is relevant for order types ZOR, ZCA, ZSM
     This batch job will have to be run manually for Day Pick orders. The end of this program should automatically kick off the delivery due list for Day Pick orders, shipping condition 02.
Business Justification:
The business requires that like order line items be consolidated to one line item prior to the order going to the warehouse for picking. This will aid in picking at the warehouse as well as result in the customer invoice not reflecting more than one line item for the same material. In the case where the customer has truly ordered more than a case, i.e;, 1 case, 2 bottles, the documents in SAP will still reflect 2 lines.

Goods issue of sales order stock

Hi,
We are implementing an MTO scenario. We are not sure what set up is required for goods movements for spl stock E?
The problem we are facing is customer number is not getting populated in Material document during PGI and COPA document?
Also we are using the standard item category ZTAN which is a copy of TAN. Please help us in understanding what set up should be done for handling Sales Order Stock.
Thanks
Chandra

Hi,
Create material (material type FERT) : MM01
Create Sales Order MTO : VA01
Make Sales order BOM : CS61
Create production order : CO08
Goods issue : MIGO/MB1A
Order Confirmation : CO15/Co11N
Deliver the Order : MB31
Deliver the Sales Order : VA02
Make invoice : VL01
The Cycle of Make to order: Steps : MTO Scenario
1. Material Creation (Make To order Material with major changes of: Item Category: 0004-make to order/assem. , or 0001-make to order)
2. Routing Creation
3. Creation of BOM
4. Sales order creation
5. Production order Scheduling, Costing, Release and Save
6. Production order Quantity confirmations for operations, Parallel task of material issue to order or to reservations (261)
7. Calculate WIP
8. Fully Produced Production Quantities will be put into stock (GR) (Spl stock indicator u201CEu201D)
9. Delivery against sales order
10. Invoicing.
11. Settlement that production order
Regards,
Saju.S

Sales order creation - data stored in which tables for customer

Hi experts,
During sales order creation, data entered during sales process is stored in various related tables. Can anyone list the tables where data is stored for customers?
Thank you

Dear Manisha
Once you saved the sale order,
- all header datas are stored in VBAK
- all item level datas are stored in VBAP
- schedule line confirmation in VBEP
- all condition types and values are stored in KONV / KONP
- Partner functions in VBPA
- Delivery related fields like Shipping Point, Delivery Date, Goods Issue etc., are all in VEPVG
thanks
G. Lakshmipathi

Automaticaly created invoice related to the sales order

Hi gurus,
I have question for you.
I will create the automatic creation of sales order via BAPi, but after creation of sales order I would like to have also automatic creation of SD invoice. Is there any setting that the invoice can be issued immediately after sales order creation or I need to use another BAPI to do this.
Is there any chance to create invoice for services (without delivery note) automaticaly after Sales order creation.
Thanks in advance
Saso

Hi gurus,
Is there any chance to create invoice for services (without delivery note) automaticaly after Sales order creation.----> Yes u can create SD invoice without Delivery note , but it depends upon ur Config Setting ?
I have question for you.
I will create the automatic creation of sales order via BAPi, but after creation of sales order I would like to have also automatic creation of SD invoice. Is there any setting that the invoice can be issued immediately after sales order creation or I need to use another BAPI to do this-->Better Option is Use Another BAPI to create SD Invoice.
Regards
Prabhu

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

BOM related issue-in sales order creation there is info message-

Similar Messages

Maybe you are looking for