Is the time column in VA05 the time the sales order created?

i have added a time column in VA05. May i know whether it is the time the sales order is created? How do i know if it it the created time? Need to know the sales order created time, for example at 7:00. Thank you

Hi
Yes this is the order creation date. You can cross check by seeing the time by checking the entry in table (VBAK-EZERT) by passing the VBAK-VBELN as the order number.
Thanks
Indranil

Similar Messages

Not able to get the Quantity and partner details in the sales order created

Hi Experts,
I am creating a followup order using the FM "BAPI_BUSPROCESSND_CREATEMULTI" . The parameters iam passing are process type, quantity , sold to party (partner) and product ID. I am able to create a sales order but the Quantity and sold to party (partner) are not getting updated in the the sales order when i check in the transaction CRMD_ORDER. When i check in the crm_orderadm_h table and give the Headerguid , i am able to see the process type and when i check in the crm_order_index table, if i give the header i am not getting the partner no and there are two lines created for one header guid. I am providing the code which i have written. Can anyone please help me in this issue??
*& Report ZCREATEORDER_LUCKY_TEST
REPORT ZCREATEORDER_LUCKY_TEST.
DATA : LV_HEADER_GUID TYPE GUID_32,
WA_HEADER             TYPE                   BAPIBUS20001_HEADER_INS,
ITAB_HEADER           TYPE STANDARD TABLE OF BAPIBUS20001_HEADER_INS,
ITAB_CREATED_PROCESS TYPE STANDARD TABLE OF BAPIBUS20001_HEADER_INS,
ITAB_OBJECTS_TO_SAVE TYPE STANDARD TABLE OF BAPIBUS20001_GUID_DIS,
ITAB_PARTNER          TYPE STANDARD TABLE OF BAPIBUS20001_PARTNER_INS,
LT_PRODUCT_I          TYPE STANDARD TABLE OF BAPIBUS20001_ITEM,
WA_PRODUCT_I          TYPE                   BAPIBUS20001_ITEM,
LT_SCHEDLIN_I         TYPE STANDARD TABLE OF BAPIBUS20001_SCHEDLIN,
WA_SCHEDLIN_I         TYPE                   BAPIBUS20001_SCHEDLIN,
ITAB_INPUT_FIELDS     TYPE TABLE OF          bapibus20001_input_fields,
ls_inputfields        TYPE                   bapibus20001_input_fields,
WA_PARTNER            TYPE                   BAPIBUS20001_PARTNER_INS,
ITAB_RETURN           TYPE                   STANDARD TABLE OF BAPIRET2,
WA_OBJECTS_TO_SAVE    LIKE                   LINE OF ITAB_OBJECTS_TO_SAVE,
ITAB_PRICING          TYPE STANDARD TABLE OF BAPIBUS20001_PRICING,
WA_PRICING            TYPE                   BAPIBUS20001_PRICING,
*To store the Objects to be saved.
WA_CREATED_PROCESS    LIKE LINE OF ITAB_CREATED_PROCESS,
ITAB_SAVED_OBJECTS    TYPE STANDARD TABLE OF BAPIBUS20001_OBJECT_ID,
WA_SAVED_OBJECTS      LIKE LINE OF ITAB_SAVED_OBJECTS,
GC_X type c.
gc_x = 'x'.
CALL FUNCTION 'GUID_CREATE'
IMPORTING
    ev_guid_32 = lv_header_guid.
CLEAR : WA_HEADER.
* Passing the respective values from the Header table to internal table.
WA_HEADER-GUID          = LV_HEADER_GUID.
WA_HEADER-PROCESS_TYPE = 'ZTA'.
APPEND WA_HEADER TO ITAB_HEADER.
*Appending the values to the ITAB_HEADER.
*appending orderadm_i to input fields
* ls_inputfields-ref_guid = LV_HEADER_GUID.
* ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'ORDERADM_I'.
ls_inputfields-ref_handle = '0000000001'.
* ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'ORDERED_PROD'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
CLEAR ls_inputfields.
* ls_inputfields-ref_guid = LV_HEADER_GUID.
* ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'ORDERADM_I'.
* ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'MODE'.
ls_inputfields-ref_handle = '0000000001'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
CLEAR ls_inputfields.
****** CHANGES MADE
* ls_inputfields-ref_guid = LV_HEADER_GUID.
* ls_inputfields-REF_KIND = 'B'.
ls_inputfields-objectname = 'SCHEDLIN'.
ls_inputfields-ref_handle = '0000000001'.
ls_inputfields-fieldname = 'LOGICAL_KEY'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
CLEAR ls_inputfields.
* ls_inputfields-ref_guid = LV_HEADER_GUID.
* ls_inputfields-REF_KIND = 'B'.
ls_inputfields-objectname = 'SCHEDLIN'.
ls_inputfields-ref_handle = '0000000001'.
* ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'QUANTITY'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
CLEAR ls_inputfields.
* ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'B'.
ls_inputfields-objectname = 'SCHEDLIN_I'.
ls_inputfields-ref_handle = '0000000001'.
* ls_inputfields-logical_key = ' '.
* ls_inputfields-fieldname = 'MODE'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
CLEAR ls_inputfields.
****** CHANGES MADE
WA_PARTNER-REF_GUID = LV_HEADER_GUID.
WA_PARTNER-REF_KIND = 'A'.
WA_PARTNER-REF_PARTNER_HANDLE = '0001'.
WA_PARTNER-PARTNER_FCT = '00000001'.
WA_PARTNER-PARTNER_NO = '10017'.
WA_PARTNER-KIND_OF_ENTRY = 'C'.
WA_PARTNER-NO_TYPE = 'BP'.
WA_PARTNER-DISPLAY_TYPE = 'BP'.
APPEND WA_PARTNER TO ITAB_PARTNER.
*"ADDING VALUES TO CT_ORDERADM_I
wa_product_i-header        = lv_header_guid.
wa_product_i-handle        = '0000000001'.
wa_product_i-ordered_prod = '12000014'.
wa_product_i-mode          = 'A'.
APPEND wa_product_i TO lt_product_i.
*"ADDING VALUES TO IT_SCHEDLIN_I
wa_schedlin_i-GUID    = LV_HEADER_GUID.
wa_schedlin_i-quantity   = '30'.
wa_schedlin_i-handle = '0000000001'.
wa_schedlin_i-mode = 'A'.
APPEND wa_schedlin_i TO lt_schedlin_i.
* wa_schedlin_i-schedlines = lt_schedlines.
*"ADDING VALUES TO WA_PRICING
wa_PRICING-REF_GUID    = LV_HEADER_GUID.
wa_PRICING-REF_KIND   = 'A'.
* wa_schedlin_i-handle = '0000000001'.
APPEND wa_PRICING TO ITAB_PRICING.
* wa_PRICING-REF_GUID    = LV_HEADER_GUID.
wa_PRICING-REF_KIND   = 'B'.
wa_schedlin_i-handle = '0000000001'.
APPEND wa_PRICING TO ITAB_PRICING.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'PARTNER'.
ls_inputfields-logical_key = '0001'.
ls_inputfields-fieldname = 'REF_PARTNER_HANDLE'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
CLEAR ls_inputfields.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'PARTNER'.
ls_inputfields-logical_key = '0001'.
ls_inputfields-fieldname = 'PARTNER_FCT'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
CLEAR ls_inputfields.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'PARTNER'.
ls_inputfields-logical_key = '0001'.
ls_inputfields-fieldname = 'PARTNER_NO'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
CLEAR ls_inputfields.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'PARTNER'.
ls_inputfields-logical_key = '0001'.
ls_inputfields-fieldname = 'NO_TYPE'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
CLEAR ls_inputfields.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'PARTNER'.
ls_inputfields-logical_key = '0001'.
ls_inputfields-fieldname = 'DISPLAY_TYPE'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
CLEAR ls_inputfields.
    ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'PARTNER'.
ls_inputfields-logical_key = '0001'.
ls_inputfields-fieldname = 'KIND_OF_ENTRY'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
CLEAR ls_inputfields.
CALL FUNCTION 'BAPI_BUSPROCESSND_CREATEMULTI'
TABLES
    HEADER          = ITAB_HEADER
    ITEM            = lt_product_i
    RETURN          = ITAB_RETURN
    PARTNER         = ITAB_PARTNER
    INPUT_FIELDS    = ITAB_INPUT_FIELDS
    CREATED_PROCESS = itab_created_process
    SCHEDULELINE    = lt_schedlin_i
    PRICING         = ITAB_PRICING.
READ TABLE ITAB_CREATED_PROCESS INTO WA_CREATED_PROCESS WITH KEY GUID = LV_HEADER_GUID BINARY SEARCH.
WA_OBJECTS_TO_SAVE-GUID = WA_CREATED_PROCESS-GUID.
* Appending the Guid of the contract to be saved to the internal table
APPEND WA_OBJECTS_TO_SAVE TO ITAB_OBJECTS_TO_SAVE.
CALL FUNCTION 'BAPI_BUSPROCESSND_SAVE'
EXPORTING
    update_task_local = space
    save_frame_log    = GC_X
TABLES
    objects_to_save   = itab_objects_to_save
    saved_objects     = itab_saved_objects
    return            = itab_return.
* Calling the Standard BAPI to Commit the transcation.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
WRITE: / 'HEADER GUID: ',lv_header_guid.
Any inputs will be highly appreciated!!
Thanks a lot in Advance.
Lakshman.

solved

NO MATERIALs in the Sales order created through inbound idoc file

hi,
i have maintained the customer material number as well the SAP Material number in the tcode VD51,but still the inbound
idoc type ORDERS03 is posting the application document(Sales order) without the materials.
for instance,
I have cust.material as CUSTMAT1 in the idoc file.
I have maintained the CUSTMAT1 as cust material and 1001 as material no in VD51.
After posting the inbound idoc file using RSEINB00 prg,the idoc is created and i can see the CUSTMAT1 in the material segment field
The Sales order is created successfully ,but without the materials.
i need the application document has to be posted with materialsm,can any one help me to solve this issue.?
Thanks

Hi ganesh ram
In order to determine the Material Number with you custom material then you needs to have some configurations.
Check with your Functional consultant to add the Access sequence for determining the Material Number with you custom material
In Sale order processes...
Thanks
Ramesh

Multiple ship to party address default setting in the " sales order creat

we use the SAP ECC 6.0,
I've a problem about the "ship to party" in the sales order creation,
the customer have 3 ship to party,
the pop up "Partner selection", default show is: "Title" , "Name1"....
But I want to default to show the "Street"
I check the sap notes: 302835, and add the "SD_VARIANT_MAINTAIN" = A in my user profile.
But seems can't working,
when click the right mouse button. A menu can't displayed.
Does anyone have the experience, Thanks.

It seems so strange ...
First of all you need to set the ALV administrator parameter among the parameters of your user-id
System-> User Profile> Own Data> Parameters
add the parameter "SD_VARIANT_MAINTAIN" = A in your user profile and SAVE
After that, execute VA01 again; when the ship to party selection pop-up appears, place your cursor at a point on the screen and just the hotspot appears , click with the right mouse button in order to open the context menu.
The "Administration" function would serve only to set the default display variant; the functions "Current Layout", "Save Layout" allow you to create the variant with the needed fields (the popup is an ALV .... )
Try to execute the described steps and give us asap a feedback...
Regards,
Andrea

User Exit in the Sales order create BAPI

Hi,
Can some one help me in telling if there exists a user exit for the BAPI '/AFS/BAPI_SALESORDER_CREATE'.
This is urgent. So, pls. throw some light on this.
Thanks in advance.

Hi
User Exits In Sales Document Processing
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.

Copy the Purchase order # to the Sales order created with reference

Generally if you create a new sales order with reference to a pre-existing sales-order, then the PO# does not get copied.
What would you have to do in-order to get the PO# copied into the new sales order ?
Thanks

Dear Noel,
As per the standard it will not get copy if you want you need to take help from the technical people (ABAPers) they may able tohelp you on that.
I hope it will help you
Regards,
Murali.

Run time of sales order

Hi,
My requirement is that the client wants to know the run time in seconds for saving sales order. That is from the time VA01 is opened and data entered and to the time the document gets saved. Is this requirement possible?
Thanks,
Alex.

Hi,
Thanks for your immediate replies. Let me be more clear with the requirement. The run time (In secs) must be updated in a custom table along with the sales order created. Is this possible? Should i have to create a custom function module IN UPDATE TASK for this? Can someone suggest me the steps to be followed please?
Thanks,
Alex

BAPI to get the Sales order line item details

Hi,
My program gets Sale sorder and item as the input and I need to fetch all the item (Given item) details for this Sales Order from VBAP. Is there any BAPI to get the item details?

Hi,
This is a sample code of BAPI.Try to map it to your requirement.This is not related to vendor.This is related to sales order.
Constants
CONSTANTS: c_contract LIKE vbak-vbeln VALUE '0020000720',
c_item LIKE vbap-posnr VALUE '000010'.
Structures
Structure to hold BAPI Header
DATA: st_bapisdhd1 LIKE bapisdhd1.
Internal Tables
Sales Order Create BAPI Return Messages
DATA: tbl_return TYPE STANDARD TABLE OF bapiret2
WITH HEADER LINE.
Sales Order BAPI Line Item
DATA: tbl_bapisditm TYPE STANDARD TABLE OF bapisditm
WITH HEADER LINE.
Sales Order BAPI Line Item
DATA: tbl_bapisditmx TYPE STANDARD TABLE OF bapisditmx
WITH HEADER LINE.
Sales Order BAPI Pricing Conditions
DATA: tbl_bapicond TYPE STANDARD TABLE OF bapicond
WITH HEADER LINE.
Sales Order BAPI Partner Functions
DATA: tbl_bapiparnr TYPE STANDARD TABLE OF bapiparnr
WITH HEADER LINE.
Sales Order BAPI Schedule Lines
DATA: tbl_bapischdl TYPE STANDARD TABLE OF bapischdl
WITH HEADER LINE.
Sales Order BAPI Schedule Lines
DATA: tbl_bapischdlx TYPE STANDARD TABLE OF bapischdlx
WITH HEADER LINE.
Sales Order BAPI Pricing Conditions
DATA: tbl_bapicondx TYPE STANDARD TABLE OF bapicondx
WITH HEADER LINE.
Customer Enhancement for VBAK, VBAP, VBEP
DATA: tbl_bapiparex TYPE STANDARD TABLE OF bapiparex
WITH HEADER LINE.
Table to hold BAPI Detail Conditions
DATA: tbl_bapisdcond TYPE STANDARD TABLE OF bapisdcond
WITH HEADER LINE.
Table to hold Return Messages from Sales Order Change BAPI
DATA: tbl_return_chg TYPE STANDARD TABLE OF bapiret2
WITH HEADER LINE.
Variables
DATA: g_vbeln_created LIKE vbak-vbeln,
g_valid_contract TYPE c,
g_cont_price_date TYPE d.
Start of Selection
START-OF-SELECTION.
PERFORM validate_contract.
PERFORM create_sales_ord.
PERFORM update_sales_ord.
End of Selection
END-OF-SELECTION.
PERFORM write_output_report.
Subroutines
*& Form create_sales_ord
Create the Sales Order
FORM create_sales_ord .
PERFORM populate_bapi_tables.
PERFORM call_create_sales_ord_bapi.
ENDFORM. " create_sales_ord
*& Form populate_bapi_tables
Fill up the BAPI Tables
FORM populate_bapi_tables .
PERFORM populate_bapi_header.
PERFORM build_bapi_partners.
PERFORM build_bapi_items.
PERFORM build_bapi_sched_lines.
ENDFORM. " populate_bapi_tables
*& Form populate_bapi_header
Build BAPI Header Details
FORM populate_bapi_header .
CLEAR st_bapisdhd1.
st_bapisdhd1-doc_type = 'ZOC'. "Order type
st_bapisdhd1-sales_org = '026'. "Sales Org
st_bapisdhd1-distr_chan = '00'. "Dist Channel
st_bapisdhd1-division = '00'. "Division
st_bapisdhd1-purch_no_c = 'Cust Po No'. "Cust PO No
st_bapisdhd1-name = 'Orderer'. "Name of Orderer
st_bapisdhd1-ord_reason = ''. "Order Reason
st_bapisdhd1-sales_off = '3001'. "Sales Office
st_bapisdhd1-sales_grp = '301'. "Market Area
IF g_valid_contract = 'X'.
st_bapisdhd1-price_date = g_cont_price_date.
ENDIF.
ENDFORM. " populate_bapi_header
*& Form build_bapi_partners
Build BAPI Partner Functions
FORM build_bapi_partners .
CLEAR tbl_bapiparnr.
tbl_bapiparnr-partn_role = 'AG'.
tbl_bapiparnr-partn_numb = '0000100750'.
APPEND tbl_bapiparnr.
CLEAR tbl_bapiparnr.
tbl_bapiparnr-partn_role = 'WE'.
tbl_bapiparnr-partn_numb = '0000504472'.
APPEND tbl_bapiparnr.
ENDFORM. " build_bapi_partners
*& Form build_bapi_items
Build The BAPI Line Items
FORM build_bapi_items .
DATA: l_matnr LIKE mara-matnr.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = '10000072'
IMPORTING
output = l_matnr.
CLEAR tbl_bapisditm.
tbl_bapisditm-itm_number = c_item.
IF g_valid_contract = 'X'.
tbl_bapisditm-ref_doc = c_contract.
tbl_bapisditm-ref_doc_it = c_item.
tbl_bapisditm-ref_doc_ca = 'G'. "Contract
ENDIF.
tbl_bapisditm-material = l_matnr.
tbl_bapisditm-plant = '3012'.
tbl_bapisditm-target_qty = '5.000'.
tbl_bapisditm-target_qu = 'M3'.
tbl_bapisditm-item_categ = 'ZZOC'.
tbl_bapisditm-sales_dist = '301'.
tbl_bapisditm-dlv_prio = '02'.
tbl_bapisditm-prc_group5 = '080'.
tbl_bapisditm-cust_mat35 = 'kdmat'.
tbl_bapisditm-route = 'TESYS'.
tbl_bapisditm-usage_ind = 'CIV'.
APPEND tbl_bapisditm.
CLEAR tbl_bapisditmx.
tbl_bapisditmx-itm_number = c_item.
tbl_bapisditmx-ref_doc = 'X'.
tbl_bapisditmx-ref_doc_it = 'X'.
tbl_bapisditmx-ref_doc_ca = 'X'.
tbl_bapisditmx-material = 'X'.
tbl_bapisditmx-updateflag = 'I'.
tbl_bapisditmx-plant = 'X'.
tbl_bapisditmx-target_qty = 'X'.
tbl_bapisditmx-target_qu = 'X'.
tbl_bapisditmx-item_categ = 'X'.
tbl_bapisditmx-sales_dist = 'X'.
tbl_bapisditmx-dlv_prio = 'X'.
tbl_bapisditmx-prc_group5 = 'X'.
tbl_bapisditmx-cust_mat35 = 'X'.
tbl_bapisditmx-usage_ind = 'X'.
tbl_bapisditmx-route = 'X'.
APPEND tbl_bapisditmx.
ENDFORM. " build_bapi_items
*& Form build_bapi_sched_lines
Build the BAPI Schedule Lines
FORM build_bapi_sched_lines .
CLEAR tbl_bapischdl.
tbl_bapischdl-itm_number = c_item.
tbl_bapischdl-req_qty = '1'.
tbl_bapischdl-req_date = sy-datum.
APPEND tbl_bapischdl.
ENDFORM. " build_bapi_sched_lines
*& Form build_bapi_conditions
Pull the BAPI Pricing Conditions from the Contract
FORM build_bapi_conditions .
LOOP AT tbl_bapisdcond.
CLEAR tbl_bapicond.
MOVE-CORRESPONDING tbl_bapisdcond TO tbl_bapicond.
APPEND tbl_bapicond.
CLEAR tbl_bapicondx.
tbl_bapicondx-itm_number = tbl_bapicond-itm_number.
tbl_bapicondx-cond_st_no = tbl_bapicond-cond_st_no.
tbl_bapicondx-cond_count = tbl_bapicond-cond_count.
tbl_bapicondx-cond_type = tbl_bapicond-cond_type.
tbl_bapicondx-updateflag = 'I'.
tbl_bapicondx-cond_value = 'X'.
tbl_bapicondx-currency = 'X'.
tbl_bapicondx-cond_unit = 'X'.
tbl_bapicondx-cond_p_unt = 'X'.
tbl_bapicondx-varcond = tbl_bapicond-varcond.
APPEND tbl_bapicondx.
ENDLOOP.
ENDFORM. " build_bapi_conditions
*& Form call_create_sales_ord_bapi
Call the Sales Order Create BAPI
FORM call_create_sales_ord_bapi .
CLEAR g_vbeln_created.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
EXPORTING
order_header_in = st_bapisdhd1
IMPORTING
salesdocument = g_vbeln_created
TABLES
return = tbl_return
order_items_in = tbl_bapisditm
order_items_inx = tbl_bapisditmx
order_partners = tbl_bapiparnr
order_schedules_in = tbl_bapischdl.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
wait = 'X'.
ENDFORM. " call_create_sales_ord_bapi
*& Form update_sales_ord
Update the newly created Sales Order with the Pricing Conditions
from the Contract
FORM update_sales_ord .
CHECK g_valid_contract EQ 'X'.
PERFORM get_contract_details.
PERFORM build_bapi_conditions.
PERFORM call_change_sales_ord_bapi.
ENDFORM. " update_sales_ord
*& Form get_contract_details
Get Contract Details
FORM get_contract_details .
Need to manually get the relevant Pricing Conditions as the BAPI
BAPISDORDER_GETDETAILEDLIST causes problems when we call the BAPI
BAPI_SALESORDER_CREATEFROMDAT2 and BAPI_SALESORDER_CHANGE (I think
this is due to the fact that these BAPIs belong to the same Function
Group and there must be some common structures that are not cleared
causing us all sorts of grief when we try and call the next BAPI)
DATA: tbl_konv TYPE STANDARD TABLE OF konv WITH HEADER LINE.
DATA: tbl_komv TYPE STANDARD TABLE OF komv WITH HEADER LINE.
DATA: tbl_vbak TYPE STANDARD TABLE OF vbak WITH HEADER LINE.
Pricing Condition Master
DATA: BEGIN OF tbl_t685a OCCURS 0,
kschl LIKE t685a-kschl,
kaend_wrt LIKE t685a-kaend_wrt,
END OF tbl_t685a.
SELECT *
INTO TABLE tbl_vbak
FROM vbak
WHERE vbeln = c_contract.
READ TABLE tbl_vbak INDEX 1.
SELECT *
INTO TABLE tbl_konv
FROM konv
WHERE knumv = tbl_vbak-knumv AND
kposn = c_item.
CHECK sy-subrc EQ 0.
We now need to make sure we only bring across the Condition Types that
are EDITABLE. If we bring across non editable conditions (such as
'ZPR1') the Change Sales Order BAPI will fail
SELECT kschl kaend_wrt
INTO TABLE tbl_t685a
FROM t685a
FOR ALL ENTRIES IN tbl_konv
WHERE kappl EQ 'V' AND "Sales
kschl EQ tbl_konv-kschl AND
kaend_wrt EQ 'X' AND "Value is Editable
kmanu NE 'D'. "Process manually
Prepare for Binary Search
SORT tbl_t685a BY kschl.
LOOP AT tbl_konv.
READ TABLE tbl_t685a WITH KEY kschl = tbl_konv-kschl BINARY SEARCH.
IF sy-subrc EQ 0.
MOVE-CORRESPONDING tbl_konv TO tbl_komv.
APPEND tbl_komv.
ENDIF.
ENDLOOP.
CHECK NOT tbl_komv[] IS INITIAL.
Map KOMV into the more BAPI friendly BAPISDCOND structure
CALL FUNCTION 'MAP_INT_TO_EXT_STRUCTURE'
TABLES
fxvbak = tbl_vbak
fxkomv = tbl_komv
fxbapikomv = tbl_bapisdcond
EXCEPTIONS
entry_missing = 1
OTHERS = 2.
ENDFORM. " get_contract_details
*& Form call_change_sales_ord_bapi
Call the Change Sales Order BAPI
FORM call_change_sales_ord_bapi .
DATA: st_head_chg LIKE bapisdh1x,
st_logic_switch TYPE bapisdls.
CHECK NOT g_vbeln_created IS INITIAL.
CHECK g_valid_contract EQ 'X'.
st_head_chg-updateflag = 'U'.
st_logic_switch-cond_handl = 'X'.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
salesdocument = g_vbeln_created
order_header_inx = st_head_chg
logic_switch = st_logic_switch
TABLES
return = tbl_return_chg
conditions_in = tbl_bapicond
conditions_inx = tbl_bapicondx.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
wait = 'X'.
ENDFORM. " call_change_sales_ord_bapi
*& Form write_output_report
Produce Output Report
FORM write_output_report .
IF NOT g_vbeln_created IS INITIAL.
WRITE:/ 'Success! Sales Order', g_vbeln_created, 'was created!'.
ELSE.
WRITE:/ 'Failure! Sales Order was not created!'.
ENDIF.
SKIP.
WRITE:/ 'Sales Order Create Log'.
LOOP AT tbl_return.
WRITE:/ tbl_return-type, tbl_return-id, tbl_return-number,
tbl_return-message.
ENDLOOP.
SKIP.
WRITE:/ 'Sales Order Change Log'.
LOOP AT tbl_return_chg.
WRITE:/ tbl_return_chg-type, tbl_return_chg-id,
tbl_return_chg-number, tbl_return_chg-message.
ENDLOOP.
ENDFORM. " write_output_report
*& Form validate_contract
Make sure that the Contract is Valid
FORM validate_contract .
DATA: l_gueen LIKE vbak-gueen,
l_prsdt LIKE vbkd-prsdt.
SELECT SINGLE vbakgueen vbkdprsdt
INTO (l_gueen, l_prsdt)
FROM vbak
INNER JOIN vbkd
ON vbakvbeln = vbkdvbeln
WHERE vbak~vbeln = c_contract AND
vbkd~posnr = '000000'.
IF sy-datum LE l_gueen.
Contract is valid! Set Order Price Date
g_valid_contract = 'X'.
g_cont_price_date = l_prsdt.
ENDIF.
ENDFORM. " validate_contract
Regards
Rajesh Kumar

No condition update from the sales orders exist - VK322 Message

Hello All,
I have activated " Condition Index" & " Condition Update" flag for one of my discount condition type and then created it's condition record along with scales on three levels. The condition type which I mentioned above is set as " Value Scale" in Scale Basis for checking the document value and apply the applicable discount percentage.
I have created three sales orders wherein the discount percentage is getting applied as per my condition record ( so, the document value is getting accumulated and compared with the condition record correctly ) but when I try to check the cumulative values ( ctrl +shift + F4 ) from the condition record, I get information message " VK322" mentioned in the subject.
VK322 -
No condition update from the sales orders exist
Message no. VK322
Diagnosis
The following causes are possible:
1. There are no sales orders for the condition record that you selected.
2. Updating condition records in the sales order entry is not active.
Procedure
Concerning 1:
Check the sales orders created for the condition record that you selected.
Concerning 2:
Activate the updating for condition records in the sales order entry.
I have checked everything in SPRO for this but could not find anything which can give me a clue to resolve this problem, especially " Concerning 2" part of this message.
My requirement > To be able to see the cumulative values from condition record.
Also, in which table the accumulated values get stored?
Appreciate your expert advise on this issue.
Regards,
Hrishi
Edited by: Hrishikesh Bhalwankar on Sep 13, 2011 1:59 AM

Hello Everyone,
I would like to thank each one of you for giving valuable inputs in regard to my requirement and I would like to let you know that I am able to achieve the results as per the expectation.
I would also like to share some key things which I did ( with the help of all your expert inputs ) due to which the requirement is met:-
1. Activation of ' Condition Index, Condition Update' in V/06 for the discount condition type.
2. Maintained ' B - Value Scale' in Scale Basis for the said condition type in V/06 - my requirement was to check against a value to apply the necessary scale base percentage.
3. Activation of ' S071' info structure via OM01
4. Condition record maintenance as per the required scales.
4. Written a new routine to check the accumulated condition base value from S071 along with the current document condition base value.
5. Put this routine in ' Scale Formula' in V/06.
This is giving me the perfect results for the correct application of the discount.
Just last question - How to re-organize the S071 info structure as I tried to re-organize it with Standard Program ' RV15F001' but it is not re-organizing this info structure... Any idea on this?
Thanks a lot friends for all your advice...
Regards,
Hrishi
Edited by: Hrishikesh Bhalwankar on Oct 11, 2011 2:11 AM

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.

Possibility of addition creation time in the sales order over view screen

Hi,
Is there a possibility of adding the creation time in the sales order overview screen in VA01/2/3.
thank you

hi,
this is to inform you that,
contact your ABAPER for this is to find out if there any possibility making time field mandatory if it is there in Standard SAP. there in VBAK table i am able to see VBAK - ERZET
or
if it is not available then you need to go for field exit.
hope this helps.
balajia
Edited by: balaji timmampalli achari on Nov 30, 2010 6:11 AM

Selecting multiple products at a time in the sales order

Hello Gurus,
Is there a way we can select multiple items at the same time in the sales order..
User wants to select multple items at the same time.... any possibility???
Regards,
Pavan P.

Hi Pavan,
If I understand you correctly, you'd like a predefined list of items you can pick from during order processing?
Have you tried Item Proposal?
Create the Item Proposal type (T Code: VOV8).
Then create the item list (TCode: VA51). You can call this list everytime you create the sales order (doc. type defined and assigned by you)
Use the "Proposed Items" button (first one on the header, extreme left) to pick from the list and have multiple items entered at one go.
Hope this was useful.
Cheers.

Limiting the time when Sales Orders can be confirmed on the same day

Hello Gurus. The business has a requirement where they want to limit the time of the day when they can confirm sales orders on the same day.
So, when they receive a sales order, they want that if the order is received after a certain time (e.g. 14:00) then it cannot be confirmed for that same day, it can only be confirmed the next day.
How can I implement this limitation?

Fernando,
Let me restate your requirement so that I understand your question:
A Sales order is created 'today' with a requested delivery date of 'today'.
There exists adequate material in Stock to confirm the order.
You want the confirmed date to be 'some-amount-of-time-later-than-now"
(say 18 hours or so)
Which confirmed date in the sales order are you talking about?
Confirmed Material Availability date?
Confirmed Loading date?
Confirmed Transportation planning date?
Confirmed Goods Issue date?
Confirmed Delivery Date?
Many people with this requirement use 'delivery scheduling', and add a half day or so in pick/pack processing time. This means that you are recognizing that it takes a bit of time to create the delivery notice, print the shipping papers, pick and pack the parts, and get them ready for the carrier to ship. So, for an order entered 'now', it wouldn't be due to ship from your warehouse until 'a half day from now'.
To enable Delivery scheduling IMG>SD>Basic Functions>Delivery scheduling and transportation scheduling>Define scheduling by sales document type. Select the relevant ordertypes, tick delivery scheduling.
If this is already selected, then you can increase the pick/pack processing time of the shipping point in IMG transaction OVLZ. It can be set to a fraction of a day (2 decimal points).
Regards,
DB49

Query needed to find what time a sales order was closed

Hi to All,
Need to find when a sales order was closed. Meaning the exact time. I know the flags that needed to be considered. But what table/column holds the exact time that the sales order was closed.
Thanks

If your workflow process details are not purged below query end_date will be order closed date.
select a.instance_id
, to_char(b.begin_date, 'DD-MON-RR HH24:MI:SS') begin_date
,to_char(b.end_date, 'DD-MON-RR HH24:MI:SS') end_date
, a.process_name process
from wf_process_activities a, wf_item_activity_statuses b
where b.item_type        = 'OEOH'
and   b.item_key     in (select to_char(header_id) from oe_order_headers_all where order_number = <Ordrer_num>)
and a.process_name = 'CLOSE_HEADER_PROCESS'.
and   b.process_activity = a.instance_idIn R12 if you do not have any customizations ,
Current close process defines wake up time as last day of month, there is no time component.
So order will be eligible from midnight of the last day of the month.
First run of Workflow background process program for item type OEOH should be closing them.
For example : If the Wait activity in 'Close - Order' process encountered first time on 09-May-2013(Any time in the month of May), then Wake up time will be last day of current month I.e. 31-May-2013 00:00.

Product hierarchy is not being maintained in the sales order material

Hi,
I have an issue where the product hier is not being maintained in the sales order for some of the materials although the material master has the prod hier maintained.. The main program is SAPMV45A and I have checked all the exits in MV45AFZZ. In none of these exits the PRODH field in XVBAP is being populated. I would like top know if anyone has faced a problem like this.
cheers
Aveek

Hi,
Thanks for your suggestion. The poduct hierarchy is maintained in the material master but not being picked up at the time of creating the sales order. I have found the solution and coding has to be done in the MV45AFZZ.
cheers
Aveek

Is the time column in VA05 the time the sales order created?

Similar Messages

Maybe you are looking for