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,

Similar Messages

Automatic Sales order creation from IDOC generated in another SAP instance?

Hi,
I have been trying to create Sales ordes in a seperate SAP instance, through the Purchase order generated in another Instance.
The Purchase order generated, passes the informtion through an IDOC to another SAP instance, I am getting the following error
" VKORG, VTWEG, SPART cannot be determined for customer 0000001000 ,Vendor000200038 "
It is Message No VG204 , Status Record 51
Please help to solve the problem.
Regards,
Chamandeep

SAP Xpert friends,
I really need help in figuring out this error I get when I send an IDoc from external system to SAP.
Here is what I do....
create empty idoc of type ORDERS01
idoc.MESTYP = "ORDERS";
idoc.SNDPRN = "1171";
idoc.SNDPRT = "KU";
idoc.MANDT = "400";
idoc.SNDPFC = "AG";
idoc.MESCOD = " ";
idoc.MESFCT = " ";
idoc.TEST = " ";
create segment of type E1EDK01
add field MENGE with a value
add segment e1edp01 to idoc
create segment of type E1EDP19
add field QUALF with a value to segment
add field IDTNR with a value to segment
add segment E1EDP19 to idoc
send idoc
When I check WE02 in SAP, I can see the idoc, but
get this error
Here are all the STATUS RECORDS
50 IDoc added
64 IDoc ready to be transferred to application
62 IDoc passed to application
51 Error: Application document not posted
 VKORG, VTWEG, SPART cannot be determined
 for customer 0000001171 , vendor
I checked on Internet and found that VOE2 can be used to setup ... this is what I have in VOE2
Customer Vendor SOrg DChl Dv
1171 0000001171 1000 00
Thanks for help...

Syntax for commiet for sales order creation from VB

syntax for commit for sales order creation from VB.
i have created sales order from vb using "sap bapi control" object, i am getting message too that sales order created of this number
BUT it will not reflect in particular table or tcode?
what should i do to commiet that sales order creation from vb while using sap bapi control.
i have tried sap function call too,
now how to commiet or is there any other way?
regards,
dushyant.

Hi,
Check this link, explains step by step.
http://abaplovers.blogspot.com/2008/02/bap-sales-order-create.html
Thanks,
Krishna

APO: RRP3 automate Production order creation from planned order ?

Hi everyone ,
I have got a business requirement in APO where in Open sale orders uploaded in R/3, needs to be converted to Planned order and subsequently to Production order in APO-PPDS tcode RRP3 at all stages. They want to automate this process rather than doing it
manually.
Can anyone tell how is this possible . Any BAPI or function module available to do this . Please help.
Regards,
Syed

Hi,
1.You need to run the heuristics Planning of standard lots SAP_PP_002 in /SAPAPO/CDPSB0 by specifying the time profile
and strategy profile, planning version and propagation range, product and location.
2. Convert PPDS Planned Orders created to process orders thru /SAPAPO/RRP7 by specifying the product location start date of the order for production order creation.
Out put of step 1- For sales order requirement, PPDS Planned orders gets created.
Out put of step 2- PPDS Planned orders are converted to production orders.
Thanks,
nandha

BAPI for Sales Order Creation from Third-party Application

Hi,
I need to create a Sales order in a SAP system from a third-party applications. Please provide the list of BAPIs/Interfaces that are involved in creation of Sales Order.

Hi,
Check this link, explains step by step.
http://abaplovers.blogspot.com/2008/02/bap-sales-order-create.html
Thanks,
Krishna

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..

Sales Order Creation from IDOC type ORDERS05

Hi experts,
 I have tried to create sales order using IDOC, using FM input IDOC_INPUT_ORDERS. But when I include segment E1EDP05 - IDOC: Document Item Conditions. I got the following errors "Conditions in IDoc E1EDP05 transferred: Check data", with status 51, and application is post.
 Fields I filled in the segment:
KSCHL
KRATE
UPRBS
MEAUN
Thanks.

SAP Xpert friends,
I really need help in figuring out this error I get when I send an IDoc from external system to SAP.
Here is what I do....
create empty idoc of type ORDERS01
idoc.MESTYP = "ORDERS";
idoc.SNDPRN = "1171";
idoc.SNDPRT = "KU";
idoc.MANDT = "400";
idoc.SNDPFC = "AG";
idoc.MESCOD = " ";
idoc.MESFCT = " ";
idoc.TEST = " ";
create segment of type E1EDK01
add field MENGE with a value
add segment e1edp01 to idoc
create segment of type E1EDP19
add field QUALF with a value to segment
add field IDTNR with a value to segment
add segment E1EDP19 to idoc
send idoc
When I check WE02 in SAP, I can see the idoc, but
get this error
Here are all the STATUS RECORDS
50 IDoc added
64 IDoc ready to be transferred to application
62 IDoc passed to application
51 Error: Application document not posted
 VKORG, VTWEG, SPART cannot be determined
 for customer 0000001171 , vendor
I checked on Internet and found that VOE2 can be used to setup ... this is what I have in VOE2
Customer Vendor SOrg DChl Dv
1171 0000001171 1000 00
Thanks for help...

Sales Order Creation from BAPI Error

Hi Friends,
I am using BAPI_SALESORDER_CREATEFROMDAT1 to create the Sales Order. But I am getting an error when I am executing the FM. I am filling the following Information and passing on the information to the BAPI FM. Details:
IMPORT PARAMETERS:
    ORDER_HEADER_IN:
            DOC_TYPE:     OR
            SALES_ORG:   BP01
            DISTR_CHAN:   01
            DIVISION:         01
            REQ_DATE_H: 29.08.2008
            PURCH_DATE: 29.08.2008
            INCOTERMS1: FH
            INCOTERMS2: PALO ALTO
            PMNTTRMS:     0001
            SHIP_COND:    01
            CURRENCY:    USD
TABLES:
     ORDER_ITEMS_IN:
             ITM_NUMBER:    10
             MATERIAL:         XXXX-6
             PLANT:               BP01
             REQ_QTY:          20
             SALES_UNIT:      EA
             ITEM_CATEG:     AGN
             SHORT_TEXT:     TEST MATERIAL
      ORDER_PARTNERS:
             PARTN_ROLE:     SH
                                        PY
                                        BP
                                        SP
             PART_NUMB:      1000
                                        1000
                                        1000
                                        1000
By using the above information, when I am executing the FM I am getting error
EXPORT PARAMETERS
      RETURN:
              TYPE:         E
              ID               AM
              NUMBER    216
              MESSAGE Incomplete address; enter country
But when I am creating it from the VA01 Transaction, I am able to create Sales Order Successfully.
Friends, please help me in this regard.
Yours
Pradeep Goli
Edited by: Pradeep Goli on Sep 8, 2008 2:56 PM

Hi,
I hope the below link will help you.
Help needed with BAPI_SALESORDER_CREATEFROMDAT1 parameters
Thanks,
Khushboo.

Sales order Creation from Purchase Order

Hi all ,
I want to create SO from PO.Is it any bapi to create SO from PO.
or other wise i will use to get PO details from this BAPI_PO_GETDETAIL and then create So from this BAPI_SALESORDER_CREATEFROMDAT2..
Iis there any bapi like BAPI_SALESDOCUMENT_COPY..

Hi
I doubt if there is one single BAPI which will serve the purpose in your case. I think you should go with the first step you mentioned. Get the PO details and then pass it to the sales BAPI.
Vishwa.

BADI:to create automatic Sales order(va01) from Scheduling Agreement(ME31L)

Gurus,
I want to create SO after Scheduling agreement creation.
I am trying to do it using BADI: ME_PURCHDOC_POSTED method Posted.
I've implemented it, and it is getting called, I am trying to create SO using SO create BAPI in the BADI.
though the same code of SO creation with schedule line Through BAPI working fine with reports, its not able to create SO with schedule line when i use it in BADI.
Point rewarded for any help.
Rgs
Ashok.
Edited by: Ashok Gupta on Mar 30, 2008 5:20 PM

i've done it.

How to trigger an Idoc from Sales order creation and change

We are trying to trigger Idoc from sales order creation and change we have done following setting mentioned below:
Follow the below steps:
1. Go to NACE transaction
2. Select V1 application and select OUTPUT TYPES
3. Select the required output type and double click on Processing routines.
4. Enter Medium as DISTRIBUTION ALE, Program as RSNASTED and Routine as ALE_PROCESSING.
5. Save it.
message type ORDERSP in the distribution model (BD64).
Follow the below steps to configure the condition records:
1. Go to NACE
2. Select V1 application and select CONDITION RECORDS
3. Select the requred output type and click on Condition records
4. Selection screen will be displayed.
5. Go for execution. In that screen enter the selection criteria. For eg Condition record is based on Sales document type. Then
Sales doc type = OR
Funt = SP
Partner = blank. It means there is no restriction on partner numbers.
Medium = A
date/time = 4
Lan = EN.
Note: partner is left blank means, the sales order of type OR can be send to all partners.
6. Save it.
We also done ALE configuration.
We are facing problem that from VA02 "No output has been selected for printing Message no. V1102"
Kindly suggest the solution.
Regards,
Sharad Dixit

Hi ,
Please check the total error description and diagnosis as below :
InVa02 enter SO go to extras->output->Header->edit.You can find a table with all the triggered output types. Choose the output type BA00 with medium Distribution ALE and go for 'Processing log'. It will show you the error description.
Please paste the diagnosis .
Thanks and Regards,
P.Bharadwaj

Automatic identification of contracts in sales order creation

Hi,
I have configured quantity contracts as a automatic determination during Sales Order creation .When i try to create sales order using va01, after i enter Sold-to Party and Material then i hit enter ,system pops up with a dialog box with list of all the contracts existing with that Sold-to Party and Material combination.
Can someone suggest me , is this pop -up window is a User Exit? If so . can you pls let me know .
I went to program SAPMV45A , which has many includes and try to check the include MV45AFZZ , but could not find out the one which i want for Pop up window.
Thanks in advance
Points are fully rewarded

Hi,
If it is a standard sap configuration..Then it may not be a user exit..
After entering the sold -to party ...Then press /H in the command button..
Then start debugging..You might the call.
OR
after the popup is displayed..Press F1 on any one of the field..In that help..press technical info button...Then check the program and screen number..
Go to SE51 with the program and screen number.Then press the where-used list button to get the calling place..
Thanks
Naren

Automatic Single Item multi-level planning on sales order creation

Hi all,
I am using strategy 50 and want planning for single item to be carried out at the time of sales order creation to avoid MRP run everytime sales order is created..In order to achieve it i checked Automatic Planning Indicator in "OVZG" for the requirement class "045" which is requirement class for sales order of strategy 50. But still unable to achieve the desired result..
Please guide me through.
best regards,
shah

HI shah,
in sales order go to Procurement tab there u will get the requirement type. system will determine requirement class based upon following criteria
1) by strategy group in material master
2) if strategy group not there then MRP group
3) if mrp group not there then material type
4) by this also not able to fine the requirement type then special rule is used with the help of item category and mrp type
5) if this also fails then it will go with item category only
6) this also fails then it will give any requirement type
hope this is clear
regards
ramakant

Sales order creation with respect to contracts

Hi Guys,
I am trying to create a saleorders with referece to contract for which in the background I configured so that during my sales order creation I see the pop-up box with all existing contracts for a specified sold-to party.
This process is so painful that order entry people have to manually select from the big list (pop up box consisting of huge list).
Is there any way so that I can automate this process insetead of selecting contracts from that list.
Regards
Krishna

Hi Ravi,
Thanks for your solution and could you please give me some more details what is the neame of the user exit.
and welcome for some more suggestions.
Thanks
Krishna
One way is to create the order with reference to the Contract and then the system will not give the pop up for the existing contracts.
The other way to automate the process is by using a userexit. Here the system should check all the existing valid contracts for this sold to party and should select the oldest or latest valid contract, as per the client choice.
Thanks,
Ravi

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

Automatic Sales Order Creation from PO in B1

Similar Messages

Maybe you are looking for