To update the status of the Sale Order through Pl/sql(backend)

Hi folks.
May I how to alter the status of Sale Order from 'Entered' to 'Awaiting for Approval' when the sale order was booked.After approval only it needs to change into 'BOOKED'.
Requirement Scenaria as follows:
Activity Status
1) Sale Order Creation Entered
2) Booking the Sale Order Awaiting For Approval
3) After Approved 'Booked'
or
4) After Rejected Rejected --- should not be available for pick and ship.
Please tell me the solution to alter the status and I had already tried both normal update statement and update through sale order API.Both didnt work.
kindly find me an appropriate solution
Note:I had already altered the OE order header workflow to go for approval when Sale order booked
Thanks in advance

Apparently, your Sales Order Type has Approval Workflow associated. Have the approver approve it from the Notifications window. Alternatively have a script to approve the workflow with userid as the approver's, in order for approval and booking.
In case of forced Booking, use OE_ORDER_PUB.PROCESS_ORDER API to pass the Order Details along with BOOKED_FLAG='Y' and FLOW_STATUS_CODE='BOOKED'.
let me know,
Dip

Similar Messages

How to make the status of a sales order complete of which PART DELIVERY

How to make the status of a sales order complete of which PARTIAL DELIVERY has already done. <b>(Assigning rejection status not accepted)</b>

Hi Gyana
There is no document with me. But I can confidently say that because I am using this functionality.
In my case I have created a Order Reason as "Short Closed". once you short close this order only the balance quantity gets rejected (provided you have already made previous delivery and PGI).
Try it in one of your test clients if you have. Once it is short Closed it wont also show in the orders due for processing in Production.
Also you can generate reports based on this if your customer wants to know how many order he has short closed, qty of item short closed etc.
Try it.
Rgds
Sunil

Find status of a sales order created using EDI IDOC

Hello everyone,
   I have IDOC created for incoming sales order using FM 'IDOC_INPUT_ORDERS'.
When a sales order is created manually iva VA01, it prevents the order from being saved when a specific error is hit unless user resolved it first.   However, when the order is created via EDI IDOC, the error is hit and it cannot be created. In the sapmv45a program, i will to say that if it is an EDI IDoc transacion for the order, let it bypass the error and create the order.
     Can anyone pls tell me how to check the status of a sales order being created using EDI IDOC ?
Sy-batch does not work.
Thank you in advance.
Joyce

Joyce,
If you pay attention the code in FM it is exporting value of da_edi_sign to memory id "SD_EDI_ACTIVE" stored in constant "da_memory_id". ('CONSTANTS: da_memory_id(13) VALUE 'SD_EDI_ACTIVE'.)
In your program you have two you have two options.
1. Declare a constant as in the FM and use that as mentioned below:
CONSTANTS: da_memory_id(13) VALUE 'SD_EDI_ACTIVE'.
IMPORT v_memid FROM MEMORY ID da_memory_id.
2. Hardcode memory id as below:
IMPORT v_memid FROM MEMORY ID 'SD_EDI_ACTIVE'.
Hope this resolves your problem.
Gajendra

How to update the condition price in sales order while creating the invoice

Hi,
How to update the condition price in the sales order to carry out the new price while creating the invoice?
While creating the invoice it should update the condition price in sales order.
Thanks,
Balaram

No, pricing is not there in delivery.
I found an exit for VF01transaction where we can update the price in order.
Can you please tell me how to update the price if I have the order, material numbers and conditions number?
Thanks,
Balaram

Changing the status of the sales order item based on reason for rejection

Hi All,
When a Sales order item is rejected then the status at the item level is changed as 'TECO'.When the reason for rejection is removed the status 'Teco' is reset.This status change can be achieved using the user exit 'MV45AFZZ'.But the exit does not allow re-atp calculation whenver a blocked item is release.I have use the exit 'MV45AFZB' ,through this the status change as well as re-atp calculation takes place.But the status changed(Based on reason of rejection) does not appear in the same screen.The change gets reflected only when the sakes order is saved and i open it again.
I want the status change to appear in the same screen.I am doing my code in the form 'userexit_check_vbap' of the exit 'MV45AFZB'. Please let me know if there are any user exits or BADI's available for the same(Changing the status of the sales order item based on reason for rejection ).
Regards,
S.Subasree

Hi subburamaiah
If you want the report you can create a separate SIS report . In that take the input field as a Reason for rejection.. and ask for the output the list of sales orders .Now when you check this user defined report you will give the reason for rejection and check what all orders got rejected on that reason for rejection.
Regards
Srinath

A FM or BAPI to update the status of a Production Order

Hello, does anybody know if there is an interface FM or BAPI to update the status of a production order. Specifically I want change the status of PP order to LKD (locked). I want to do it programmatically from an external system.
Thank you
Ernesto

Hi,
I believe you can use the FM I_CHANGE_STATUS to update the status..
where JEST-OBJNR = AUFK-OBJNR
Thanks,
Naren

Auto Approval EBP Purchase Order is not updating the status at the header

Hi There ,
We are facing an issue in EBP auto approval PO ,
The process level schema is set to Auto Approval (Standard 9CBUS2201_EX01_55)
During the PO creation , the standard schema is triggered and it gets approved .
The status of the PO in the Approval Tab is showing as Approved .
But in the docuemnt level the status is still Awaiting Approval .
While checking in SWI1 we came to know that an error has happened in the Task TS40007972
and the Guid ID of SRM Purchase is initial that has made the status(EV_STATUS) as initial .
The ERROR is from the below class & method.
Class: /SAPSRM/CL_WF_PROCESS_MGR_SBWF
Method:GET_PROCESS_DECISION_STATUS
Can anyone suggest to overcome this issue .It will be very usefull if anyone could suggest debugging possibility if any .
Regards,
Arun.

Have you tried notes?
1625513 - Workflow without approval is Awaiting approval status
1724251 - Workflow log error: CREATE_DECISION_SETS cannot be executed

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

Dates fields issue in the sales orders through IDOC

Hi all,
I'm trying to create a sales order through Inbound IDOC using IDOC_INPUT_ORDERS.
I have 2 custom fields in the sales order which are date fields.
I'm populating them from the IDOC segments(using E1EDKT1-tdid, E1EDKT2-tdline) in the user-exit just before the call trasacation statement. These dates are not coming for a few orders... but are getting populated normally for few of them.
But the tricky part is that... if I process the same IDOC for the second time.. the order created is having the dates.
My issue is that.. i need all the orders to be populated with the dates which IDOC have.
Could anyone please help me with this issue.
All the answers/replies are highly appreciated!!
Thanks for you help!

hi,
the following may be of help
There are 2 major exceptions to the batch input internal table. All text data from the segments E1EDKT1/2 and E1EDPT1/2 are not part of the batch input session. Text elements from these segments are posted directly to the data base AFTER the sales order has been created (please note: in order that item texts are posted correctly to the sales order the field POSEX from segment E1EDP01 MUST be transmitted). Also, configurable material information from the IDOC is exported to a global memory and therefore will not be part of the batch input session. Configurable material data is performed in Form CHECK_CONFIGURATION and the data is exported to global memory in the following code:
Exportiert IDOC Daten ins globale Memory
export IDOC data to global memory
call function 'CUXC_IDOC_TO_MEMORY'
       tables
            cfg_instref = xe1curef
            cfg_ref     = xe1cucfg
            inst        = xe1cuins
            part_of     = xe1cuprt
            value       = xe1cuval
       exceptions
            error       = 1
            others      = 2.
One extra piece of useful infomartion if you wish to debug the process is to set your breakpoints at the following points
for Function module IDOC_INPUT_ORDERS
include LVEDAF0F..
CALL TRANSACTION 'VA01' USING bdcdata
                            MODE input_method
                            UPDATE 'S'
                            MESSAGES INTO xbdcmsgcoll.
Now input_method is A foreground process and N for background processing but try changing it to P (pass through mode)
If you have breakpoints in va01, e.g. MV45AF0B_BELEG_SICHERN,(the part where the sales document is saved)
they will be hit, e.g
perform userexit_save_document_prepare.
perform userexit_save_document.
Lastly, don't forget using program SDJEDI , see note 380603 for more information on this
Hope this is useful
Paul Quinn

How to change the status of a production order

Dear All,
May i know how to change the status of a production order.I want to de-active the status like OPGN (Operation generated).This status is updated as there was no routing assigned to that particular production order during its creation
Thanks and Regards,
Varun Siddharth

Dear,
When you create a production order, an operation created by the system is generated automatically if no routing is used for the creation. As a result the order header receives the status HOGAN; the operation created automatically also has this status.
If you delete the operation created automatically and then do not have the status HOGAN.
To avoid this maintain the Routing for the material or delete the setting of default operation from OPJG.
Regards,
R.Brahmankar

Uploading Purchase Order Against the Sales Order through DTW

Hi Experts,
I searched the forum but could not see anything regarding this.
Can I upload Purchase Orders against the Sales Orders using DTW upload facility? Manually we do it through the Logistics Tab in Sales Order.
Thank you in advance.
Kind Regards,
IC

Hi,
You can use the BaseType, BaseEntry and BaseLine columns for this in the row level template (DLN1):
BaseType: it's the Object Type of base document (ORDR.ObjType) which is '17' in case of Sales Order
BaseEntry: it's the Document Entry of the base document (ORDR.DocEntry)
BaseLine: it's the row number of the line in the base document (RDR1.LineNum)
If you import your Delivery Notes with this info, the link to the Sales Order will be updated just as if you used Copy To in SAP.
Regards,
Nat

SPL block when changing the Address manually at Sales order level

Hello all, I hope every one doing well
I am facing one problem in SAP system, when I am chanigng the Partner address at sales order level , system giving the SPL block , without screening even though the customer is a good customer.
I checked in Img: GTS -> SAP Compliance Management->"Sanctioned Party List Screening" Service->Control Settings for "Sanctioned Party List Screening" Service->Sanctioned Party List Screening Strategy for Customs Docs tested with as " Status check of unchanged Addresses( Partner Address) and New check of changed Addresses.
I didn't find any difference. Sales order getting block for the above cases when changing the Address at Sales/Create document level.
Please let me know how to resolve it.
Is it related to configuration if yes how ? pr
do we have any OSS Notes to Rescreen the Sales orders with compliace even though changing the Address at sales order level ( ship to party address changes like Name, city, email id, of fax )?
or
do we need to do the Enhancement for Rescreening when changing the ship to party adress (changes like Name, city, email id, of fax )
manually at sales order level ?
Thanks in Advance
NVR

hello Sameer,
1. Whether your Embargo service is activated for the Country of Plant from which your order is getting shipped. -- Yes I have activated the Country under Embargo list.
2. Whether the partner function for which you changing the county detail has been added in into the Partner group which is assigned to Embargo services.( GTS)-- Assinged the Sold to Party ( AG) for PGEMB2- Partner group
3. Whether the country which u putting as Embargo has been maintianed under Embargo country list,
- yes
What I am doing exactly is , I am creating sales order with US customer master , but I am chaning the Country Key as Embargo country ( Ex: CU, SY, IR) at VA01 , or VA02 level Sales order header Partner tab level for Sold to party address ( changing only country key as embargo country) , not to ship to party ( ship to party still US country key only), at that time system not blocking the sales order as embargo.
please let me know if any once come across this sistuation..
Thanks in advance
NVR

User Exit in the change mode of Sales Order

Dear Guru's
In my requirement I want to stop the user from editing the status of Delivery block and Billing Block into the change view of Sales Order.
I have 2 users for them whenever they may see the change mode of sales order they should see Delivery and Billing Block in gray
that they should not be able to remove the block or change the block.
But I have two other users also who can release and change the Blocks.
Therefore I think mine is the User Exit case but I dont know which is the User Exit I have to give to the ABAPer
Please suggest me the User Exit, Thanks in advance for answer and Suggestions.
regards,
Vojas

Dear Vojas,
As per me User exit will be used, as there are check about the users in your requirement. Please try with in MV45AFZZ, there are seceral user exit, I guess in USEREXIT_READ_DOCUMENT may be used, ask your abaper to put a check on the current user and if the user which is not in your list of authorized one then change the Blocks in Display mode, or uneditable mode.
Thanks,
Raja

So where we see the status of this work order request

Hi All,
I have submitted work order WO00034931 in SAP for a new vendor address but it seems my approver (Andre Vabre) never received it. In SAP, its status is Submitted for Approval.
So where we see the status of this work order request
Thanks,
Kumar

Hi
You can make the price of a variant dependent on the characteristic values assigned (Pricing).You can use
variant conditions to define surcharges and discounts for a variant
Variant u2013Pricing steps
Create condition record
create a procedure where you enter the reference from the characteristic
Assign the procedures to either the characteristic values
configure the material in the sales order
The net price for the material is displayed
If a value that triggers a variant condition is selected when configuring a material in a sales order, the price of the material displayed under Net value is automatically increased or reduced.
In addition, the Conditions pushbutton is displayed.
On pressing this pushbutton,
One can see which conditions have
influenced the price.
I tried to list you as much detail as possible. Hope that you will be able to resolve your issue
Thanks

Finding the original quanitity on sales order : Select Query on CDPOS ?

Hello ABAPers,
I have created a sales order and I changed the order quantity over many times using Va02. If i want to programatically determine the orginal quantity, on the sales order when it was created , how would i determine ?
I thought, I would do a select query on CDPOS table and find out. But i found from se16 that for the Object ID - VERKBELEG and Object id = 00000XXXXX ( where XXXXX is sales order number), the VBEP and VBAP entries for Update mode shows no Old_vales and New_values.
But if i click on environment>Changes> in Va02 for that particular Sales order, I see the old and new values list.
Why is this not listed in CDPOS ? How do I progrmatically determine the original quanitity on Sales order ?
Thanks
SHK

Hi Ferry,
That FM did the trick. I ended up creating a FM myself to find the original qty and original unit. Somehow select qry on CDHDR and CDPOS, returned empty field for Old_value and new_value. Here is my FM below
FUNCTION z_sw_originalqty_on_so.
*"*"Local interface:
*" IMPORTING
*"     VALUE(I_VBELN) TYPE VBELN OPTIONAL
*"     VALUE(I_POSNR) TYPE POSNR OPTIONAL
*" EXPORTING
*"     VALUE(I_ORIGINAL_QTY) TYPE KWMENG
*"     VALUE(I_ORIGINAL_UNIT) TYPE VRKME
DATA : i_editpos TYPE TABLE OF cdred INITIAL SIZE 1 .
DATA : wa_editpos LIKE LINE OF i_editpos.
DATA : wa_editpos1 LIKE LINE OF i_editpos.
DATA : i_cdhdr   TYPE TABLE OF cdhdr INITIAL SIZE 1.
DATA : i_cdpos   TYPE TABLE OF cdpos INITIAL SIZE 1.
DATA : wa_cdhdr LIKE LINE OF i_cdhdr.
DATA : wa_cdpos LIKE LINE OF i_cdpos.
DATA : i_objid TYPE cdhdr-objectid.
DATA : delimiter(1) VALUE ' '.
DATA : lv_org_qty(127)      TYPE c,
         lv_org_unit(127)      TYPE c.
DATA : l_tabkey TYPE cdpos-tabkey.
DATA : i_flag.
CLEAR i_flag.
CONCATENATE sy-mandt i_vbeln i_posnr '0001' INTO l_tabkey.
i_objid = i_vbeln .
CALL FUNCTION 'CHANGEDOCUMENT_READ'
       EXPORTING
            objectclass                = 'VERKBELEG'
            objectid                   = i_objid
            tablekey                   = l_tabkey
            tablename                  = 'VBEP'
       TABLES
            editpos                    = i_editpos
       EXCEPTIONS
            no_position_found          = 1
            wrong_access_to_archive    = 2
            time_zone_conversion_error = 3
            OTHERS                     = 4.
IF sy-subrc <> 0.
    SELECT SINGLE bmeng INTO i_original_qty FROM vbep
                   WHERE vbeln = i_vbeln AND
                         posnr = i_posnr.
    SELECT SINGLE vrkme INTO i_original_unit FROM vbep
                   WHERE vbeln = i_vbeln AND
                         posnr = i_posnr.
ENDIF.
SORT i_editpos BY udate utime tabname fname .
LOOP AT i_editpos INTO wa_editpos.
    READ TABLE i_editpos INTO wa_editpos1
             WITH KEY tabname = 'VBEP'
                      fname   = 'WMENG'
                      CHNGIND = 'U'.
    CLEAR : i_original_qty,i_original_unit.
    IF sy-subrc EQ 0.
      SHIFT wa_editpos1-f_old LEFT DELETING LEADING space.
      SPLIT wa_editpos1-f_old AT delimiter INTO lv_org_qty lv_org_unit .
      i_original_qty = lv_org_qty.
      i_original_unit = lv_org_unit.
      i_flag = 'X'.
      EXIT .
    ENDIF.
ENDLOOP.
sy-subrc = 4.
IF sy-subrc <> 0 AND i_flag NE 'X'.
    SELECT SINGLE bmeng INTO i_original_qty FROM vbep
                   WHERE vbeln = i_vbeln AND
                         posnr = i_posnr.
    SELECT SINGLE vrkme INTO i_original_unit FROM vbep
                   WHERE vbeln = i_vbeln AND
                         posnr = i_posnr.
ENDIF.

To update the status of the Sale Order through Pl/sql(backend)

Similar Messages

Maybe you are looking for