Sales Order Creation for Advertising Management(Broadcasting) - SAP ERP 6.0

Hi all,
my scenario is to place a Order say "Commercial" and want to read the same from ERP after creating the order.
please give me a step by step solution for placing this order as i am very new to this topic.
I have gone through this link for creating an Order item
[http://help.sap.com/erp2005_ehp_04/helpdata/en/49/e98c371e558216e10000009b38f889/frameset.htm]
From where should i start for acheving the desired result as i am very new to this.
Thanks and Regards

Hi,
Refer following link;
[SAP ERP Solution Browser|http://solutionbrowser.erp.sap.fmpmedia.com/]

Similar Messages

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

Sales order creation for a project

Dear all,
I would like to know how to create quotation ,sales order, delivery and Billing for a total project. Let me explain the situation.. Customer has 4 different product.. they have 4 Plants to produce those materials.. They will sell each products individually and combination of others also. Their sales process is Customer will place an order for the total project which involves supply erection and Training. The erection and training may take 3 months to 1 year. The requirement is customer wants to create quotation and sales order creation in SAP. Also they want to map the erection and Training in SAP. They would like to capture the expenses involved during the erection and Training period. In this case excise duty, Sales Tax and service Tax all are involved in the same project.
Can any one suggest some idea
Thanks in advance
Sriram

Hi,
It is understood that your client has 4 plants for 4 different materials. Your client sells materials and service (1.Installation of equipment and 2.Training the users). Your client wants to know the cost of the sold items (Materials and services). The billings are subjected to all applicable taxes.
As you know, these requirements can be mapped in SAP by SD and PS modules.
SD Module: Whatever the customer places the order (either partially or as total), you can create quotations. The materials are finished goods (FERT) and service materials (DIEN). The pricing procedure should consider all applicable duties and taxes.
The business flow: Quotation >> Sales order >> Delivery of goods >> Billing (VF01) >> Excise Invoice >> Account receivable.
Note: To link the sales order with PS module you have to maintain respective u2018WBS Elementu2019 in the Account assignment tab of the sales order. This is used for planned revenue in PS.
Since you are supplying goods from all plants, maintain all plants to Sales organization and distribution channel combination in Assignment of Enterprise structure.
PS Module:
If the customer orders for an entire project including supply of materials, installation and training the users, create a project definition for that project in the project system. Assign a main WBS element under the project definition. Assign lower level WBS element according to your need. Under the WBS element network is assigned. Under the network activities are assigned. Under the activity there are activity elements. There are different types of activities; internal, external etc.
You can assign different WBS element for services. Under this the relevant activities are assigned.
You can budget for the project; you can assign supplementary budget if it is required.
When you release the project the Purchase requisitions are generated. The MM persons will create PO and procure the materials for the project.
All the materials required are initiated from PS. Here every activity is routed through PS including service. So, all the expenses are captured.
By settlement rule, the cost is arrived at different levels.
The configuration is to be done accordingly.
Hope this give you an idea on the subject.
Regards,
K Bharathi

Restricting Sales Order Creation for Customers with specific AccountGroup

Hi
We have 2 Accont Groups for Customers namely Actual & Prospective.
We wish to allow Enquiry / Quotation and Order creation for customers with Account Group ACTUAL and wish to allow only Enquiry and Quotation creation for customers with Account Group as Prospective.Is there anyway i can apply Sales Order creation block on an ACCOUNT GROUP on whole and not on Individual customers...
Regards
Sanjeev Bagaria

Hello
I did this through Listing Inclusion / Exclusion.
(1) We created a new Customer Group 99 for Prospective Customer
(2) We then created a new Condition table xxx with Customer Group & Material Type(as footer)
(3) We then created this new Access Sequence Customer Group / Material Type to Exclusion Procedure B00001
(4) We then assign the Exclusion Type B00001 to Sales Documents ZDOM & ZEOR our Order Sales Documetn Types
(5) And finally we created a record for Exclusion with 99 Customer Group and Material Type as FERT..
This now restricts creation of Sales Orders for all my Prospective Customers provided Customer Group is maintained in Customer Master. We are now also able to make Enquiry / Quotation and Sample Sales Order for Prospective Customers sicne we have Different Sales Document Types for all these and have assigned Exclusion only to normal Sales Order Document Type.
Thanks a lot for all the suggestions provided.
Regards
Sanjeev

Restrict Sales Order Creation for Serial Numbers already in Sles Order/Sold

We have recently implemented variant configuration and usage of serial numbers.
Facing some problems because of this.
1. If a Material is in Stock e.g Material xyz and serial number 123
System allows us to create sales order and Deliver and Invoice Serial number 124.
I have activated Indicator: Serial Number Existence Requirement thru OIS2. However it solves only part of my problem.
If for Material xyz serial number 123 is in stock but serial number 124 has also been created and assigned to material xyz but not in stock, then system allows me to create sales order, delivery and billing for material xyz and serial number 124.
When I check MMBE I see zero stock when I click on serial number I see serial 123, which is inconsistent.
How to ensure that such a situation does not happen?
Also I do not want the system to create a sales order for a material for which sales order has been created.
e.g. for material xyz and serial 1234 if sales order exists then system should not allow creation of another sales order for the same combination.
However in case of consignment orders the system should allow only the logical transactions like consignment fill up or consignment returns.
Please help.
Regards
Rajkumar Reddy

Hi
This is nothing but Creating Roles and assigning the respective authorizations to the Roles for giving the access to the related Tcodes
This has to be done by basis people
using the Transactions
PFCG
SU21
SUIM
such that every user can not create the sales order or change it.
Reward points if useful
Regards
Anji

Sales order creation for service items?

Hi,
My client is a courier company and it wants to implement sap. You offer only service how do you map in sap??. can we create sales order for service items.?. and how about the entire outbound process can be mapped?. Any ideas or insights or practical experience. Kindly share.
Regards,
Jothiswaran.

Jothiswaran,
I think it could be mapped with SAP CS - Sale of service functionality in R/3.
Rough Idea:
Create a Sales order with Service product (Mumbai2chennai) with a Task list (Routing - for each stage). Let it triggers a Service order. Confirm each stage in Service order with Truck number for tracking. Once you complete the delivery, do TECO in Service order. May be advance billing or post billing.
Try in SAP CS.
Babu

Sales order creation for past month

Hi,
we created condition record for service tax for two tax code
A1 - 12.36 % - Validity period - 01.04.2008 to 25.02.2009 &
A2- 10.26% - 26.02.2009 to 26.02.9999
Now client want to enter old January's sales order with old tax i.e 12.26
My question is it possible?
because if create order with January's pricing date then also system is taking current date with tax 10.36
which is not require
How to resolve this Issue?
Regards,
Akshay

Hi,
Thnx for reply
I already have condition record for the perion april'08 to 25.02.09
Thnx,
Akshay

How to avoid sales order creation for expired contract

Hello,
Is there any way to prevent creation of sale order reference to expired contract?
Please suggest.
Thanks,

Hi,
As Shadu says, create your own VOFM subroutine using '001' as a model and set it in VTAA. You can see in this subroutine this coding:
* Check the validity period of the reference document
if vbak-angdt > 0 and
     vbak-angdt > sy-datlo.
    write vbak-angdt to bp_datum_ausgabe.
    message w008 with bp_datum_ausgabe.
endif.
Replace the warning message (it's hardcoded) by other and use the field of date that you need.
If you need something else, dont hesitate to tell us.
Regards,
Eduardo

Sales Order Creation for Contracts

Hi,
When I execute FM 'CRMXIF_ORDER_SAVE', it is going to dump with error
"Inconsistency between Dictionary types "CRMXIF_BUSTRANS_ITEM_T". "
if someone could help me sorting this out that would be great.
I would also like to know if there is any other FMs for creation of order for contracts.
Thx,
Vinod

Hi Vinod,
You need to pass the input fields for every field you populate.
Here is the corrected code. I have marked the modifications in BOLD.
**Passing sample data to those internal tables to test.
it_organisation-dis_channel = '01'.
it_organisation-division = '01'.
it_organisation-sales_org = 'PAT'.
it_organisation-sales_org_resp = 'PAT'.
APPEND it_organisation.
*it_products-partner_prod = '28811'.
*APPEND it_products.
CALL FUNCTION 'GUID_CREATE'
IMPORTING
EV_GUID_16 =
EV_GUID_22 =
ev_guid_32 = zguid_32.
it_header-guid = zguid_32.
it_header-process_type = 'ZWK8'.
it_header-logical_system = 'C4DCLNT200'.
it_header-posting_date = '20060525'.
APPEND it_header.
<b>*HEADER INPUT FIELDS
IT_INPUT_FIELDS-REF_GUID = ZGUID_32.
IT_INPUT_FIELDS-OBJECTNAME = 'A'. (A for header and B for item)
IT_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_H'.
IT_INPUT_FIELDS-FIELDNAME = 'GUID'.
APPEND IT_INPUT_FIELDS.
IT_INPUT_FIELDS-REF_GUID = ZGUID_32.
IT_INPUT_FIELDS-OBJECTNAME = 'A'. (A for header and B for item)
IT_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_H'.
IT_INPUT_FIELDS-FIELDNAME = 'PROCESS_TYPE'.
APPEND IT_INPUT_FIELDS.
IT_INPUT_FIELDS-REF_GUID = ZGUID_32.
IT_INPUT_FIELDS-OBJECTNAME = 'A'. (A for header and B for item)
IT_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_H'.
IT_INPUT_FIELDS-FIELDNAME = 'LOGICAL_SYSTEM'.
APPEND IT_INPUT_FIELDS.
IT_INPUT_FIELDS-REF_GUID = ZGUID_32.
IT_INPUT_FIELDS-OBJECTNAME = 'A'. (A for header and B for item)
IT_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_H'.
IT_INPUT_FIELDS-FIELDNAME = 'POSTING_DATE'.
APPEND IT_INPUT_FIELDS.
ORGMAN INPUT FIELDS
IT_INPUT_FIELDS-REF_GUID = ZGUID_32.
IT_INPUT_FIELDS-OBJECTNAME = 'A'. (A for header and B for item)
IT_INPUT_FIELDS-OBJECTNAME = 'ORGMAN'.
IT_INPUT_FIELDS-FIELDNAME = 'DIS_CHANNEL'.
APPEND IT_INPUT_FIELDS.
IT_INPUT_FIELDS-REF_GUID = ZGUID_32.
IT_INPUT_FIELDS-OBJECTNAME = 'A'. (A for header and B for item)
IT_INPUT_FIELDS-OBJECTNAME = 'ORGMAN'.
IT_INPUT_FIELDS-FIELDNAME = 'DIVISION'.
APPEND IT_INPUT_FIELDS.
IT_INPUT_FIELDS-REF_GUID = ZGUID_32.
IT_INPUT_FIELDS-OBJECTNAME = 'A'. (A for header and B for item)
IT_INPUT_FIELDS-OBJECTNAME = 'ORGMAN'.
IT_INPUT_FIELDS-FIELDNAME = 'SALES_ORG'
APPEND IT_INPUT_FIELDS.
IT_INPUT_FIELDS-REF_GUID = ZGUID_32.
IT_INPUT_FIELDS-OBJECTNAME = 'A'. (A for header and B for item)
IT_INPUT_FIELDS-OBJECTNAME = 'ORGMAN'.
IT_INPUT_FIELDS-FIELDNAME = 'SALES_ORG_RESP'.
APPEND IT_INPUT_FIELDS.</b>
CALL FUNCTION 'BAPI_BUSPROCESSND_CREATEMULTI'
TABLES
header = it_header
ITEM =
ACTIVITY =
sales = it_sales
PARTNER =
organisation = it_organisation
SHIPPING =
APPOINTMENT =
TEXT =
SERVICE_OS =
STATUS =
<b>INPUT_FIELDS = IT_INPUT_FIELDS</b>
CREATED_PROCESS =
RETURN = it_return
LEAD =
OPPORTUNITY =
PRODUCT =
SCHEDULELINE =
CUSTOMER_HEAD =
CUSTOMER_ITEM =
PRICING =
PRICING_ITEM =
CONDITION_CREATE =
BILLING =
CONFIG_CFG =
CONFIG_BLB =
CONFIG_INS =
CONFIG_PRT =
CONFIG_VAL =
CONFIG_VK =
CONFIG_REF =
ADDRESS =
BILLPLAN =
BILLPLAN_DATE =
EXTENSIONIN =
DOCUMENT_FLOW =
BATCH =
PRICING_AGR_CRM =
FINPROD_ITEM =
CANCEL =
CANCEL_IR =
PRODUCT_LIST =
products = it_products
OBJECTS =
PAYPLAN =
PAYPLAN_DATE =
CONFIG_FILTER_CFG =
CONFIG_FILTER_INS =
CONFIG_FILTER_PRT =
CONFIG_FILTER_VAL =
ACTIVITY_I =
it_objectstosave-guid = it_header-guid.
APPEND it_objectstosave.
CALL FUNCTION 'BAPI_BUSPROCESSND_SAVE'
EXPORTING
update_task_local = ' '
save_frame_log = 'X'
IMPORTING
log_handle = l_log_handle
TABLES
objects_to_save = it_objectstosave
saved_objects = it_savedobjects
return = it_return.
IF NOT it_savedobjects[] IS INITIAL.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
wait = 'X'.
IMPORTING
RETURN =
ENDIF.
IF sy-subrc = 0.
ENDIF.

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

Spliting up the G/L account in time of Sales Order creation .

Hi,
I am an ABAPer. Please let me know using ABAP code how to split the G/L account in time of Sales Order creation for a Payment Card.
Shyamal.

Hiya,
Don't have the system before me, but I think the approx path is:
IMG --> Controlling --> Profitability Analysis --> Master Data --> Valuation --> Define and Assign Val Strategies (I think it is KE4U).
Look up the Val Strategy assignments and look for anything with Record Type "A".
Secondly, look for:
IMG --> controlling --> Profitability Analysis --> Actual Postings --> Active transfer of Sales Order Data
Under here, look for any assignments of Condition Types to Value Fields and Quantity Fields to COPA Value Fields (Qty.)
If these are present, they must have been put there on purpose. You should NOT JUST GO AHEAD AND DELETE them. Check why these are there and then check why these are flowing into your COPA report.
Normally COPA reports are defined by Record Type. If you used Record Type "F" in your reports, you should always get the proper PL report. However, if you assigned a combination of "F" and "A", you will find that your Order data is flowing into COPA along with the Billing data. So the third check point should be your report definition. Call up the form for the report you are running using transaction KE35 (Change Mode). Check the definition of the Sales quantity, etc. and look for any flows with Record Type "A". Since the form may be used by others, it is not a good idea to delete a form as it is. Copy the form into another and change the new one. Delete the "A" assignments and see if you get the correct result.
Broadly these are the areas you need to check. But COPA is vast and there could be other areas as well (e.g., KEDR Derivations, or some custom programs (SMOD)) which can trigger flows to COPA Value Fields.
Cheers.

Sap afs - how to customize matrix grid in sales order creation

Hello,
can anyone help to understand how to customize the matrix grid shown at sales order creation/change (VA01 - AFS Item overview tab - Matrix entry pushbutton). Here system, starting from inserted material nr, shows all possible combination from material's sales grid. The requirement asks to manage the matrix grid before it is shown to the user.
Thanks in advance for your help
maurizio

Hi
It depends on master data of your material
Max

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

Create ecatt script for one sales order creation with multiple line items

Hi ,
I want to create a ecatt script for one sales order creation with multiple line items. Preferably SAP GUI.
This selection of data will be from an external file/ variants which will have only one row of data in it.
Firstly: I have to sort the external file having same PO Numbers in an order.Group them together.
Second: I have to create sales order for those many line items having same PO Number.
Best Regard
Taranum

Hi Micky
Firstl you should upload the Line items for a particular sales Order in an Internal table
and then pass that internal table to your BAPI during your coding corresponding to a particu;lar sales order
In case of any issues pls revert back
Reward points if helpful
Regards
Hitesh

Regarding bapis for sales order creation and modification

Hi,
I am trying to create a syncbo for sales order creation, modification and display. The bapis that I am using are
1.BAPI_SALESORDER_GETLIST
2.BAPISDORDER_GETDETAILEDLIST
3.BAPI_SALESORDER_CREATEFROMDATA1
4. BAPI_SALESORDER_CHANGE
Am I using the correct bapis. When I tried to create a syncbo it gave the following errors
BAPISDORDER_GETDETAILEDLIST does not have RETURN parameter in export or tables parameter
RETURN parameter in Create BAPI Wrapper should refer to structure BAPIRET2
RETURN parameter in GetList BAPI Wrapper should refer to structure BAPIRET2
GetDetail BAPI Wrapper does not have RETURN parameter in export or tables parameter
No Export parameter referring to header structure exists in GetDetail BAPI Wrapper
No Import parameter referring to header structure exists in Create BAPI Wrapper
No Import parameter referring to header structure exists in Modify BAPI Wrapper
No Import parameter referring to a field of header structure exists in GetDetail BAPI Wrapper
No Export parameter referring to a field of header structure exists in Create BAPI Wrapper
No Tables parameter referring to item structure exists in Create BAPI Wrapper
No Tables parameter referring to item structure exists in Modify BAPI Wrapper
I am informed that the above bapis are standard bapis.
I am not sure as to why I am getting the errors.
Does the syncbo require the bapi's to be in a specific format.
What would be the header and item structures for sales order bapis
Regards
Raja Sekhar

Hi Raja,
ya , for creating Sync BOs ,our BAPI wrappers must satisfy certain conditions..
just go through this link.
u can use the standard BAPIs of SALES Order in ur Custom BAPI Wrapper
http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/what_is_a_bapi_wrapper.html
the RETURN must be of type BAPIRET2..
Regards
Kishor Gopinathan

Sales Order Creation for Advertising Management(Broadcasting) - SAP ERP 6.0

Similar Messages

Maybe you are looking for