Purchase requisition got deleted in the sales order..

Hi All,
I got stuck up with an issue in AFS.
The issue is that after creating a P.O with the help of a TAB order,the user has assigned a rejection reason at the item level in the sales order.
Then again the rejection reason was removed and now the purchase requisition is not appearing in the sales order.
Now how can i get back the purchase requisition??Is there any option to retreve the purchase requisition with the help of a correction report??
Can any one please help me out..
Thanks.

Many thanks for your answer. It help me to solve the issue.
So applying note 738171, with transaction OVB5 (or VOFM, requirements->subsequent functions->Purch.requisitions) we create one new requirement, ie RV07A900, and then we apply the rule that if we have delivery or billing block, that is, VBAK-LIFSK or VBAK-FAKSK not empty, then we set an error with a code similar to this:
            da_sy-msgid = 'Z1'.    (message class)
            da_sy-msgno = '001'.  (message number)
            error_exception = true.
and then the PR is not created.
Regards.

Similar Messages

  • Re: Purchase REquisition creation with ref to SAles Order

    Hi All,
    I need help on an issue.
    I have sales order creation and when saving Purchase REq is created at the back end. But for the sales order for item category n schedule line category combination does not allow creation of Pur Req. n pur req no. is not dislayed in Sales order.
    But I have Pur Rq created with ref to sales order.
    How is it possible.
    In Pur req  I checked the creation indiacotr, it is with ref to sales order.not manually.
    Can you please help it out..
    Regards,
    Smitha

    Hi,
    Purchase Requisition creation from Sales Order is dependent on the configuration of Schedule line category not Item category. Check configuration of Schedule line category in VOV6.
    Also to see the PR No in Sales Order, double click on the Sales line item and click on the "Purchase Requisition" button under "Schedule Lines" Tab.

  • Purchase Requisition number not changing when sales order item is rejected

    Hi all,
    I have a requirement to change the sales order status to 'TECO' when ever some reason for rejection is selected in the status tab at the item level.The status should change from 'TECO' when i remove the reason for rejection.
    The status change is happening correctly.I have achieved it using user exit.
    CASE 1 : Initially, when a new item is added in the Sales order the purchase requisition number appears in the schedule lines tab of the item level. This is as expected.
    CASE 2 :When the same item is blocked (by entering a reason for rejection in status tab of VA02 ) then the purchase requisition number is not present in the schedule lines tab.This is as expected.
    But i face the following issue.
    CASE3 : Again if the blocked item is unblocked (By removing the reason for rejection in status tab of VA02 ) then the purchase requisition number does not appear again in the schedule lines tab.The purchase requisition number is expected to appear again.
    This happens in case of DROP SHIPMENT scenario. I understand that in case of dropshipment scenario the purchase requisition number is triggered by item category and schedule lines only.
    I tried to make the changes(to change the status ) in user exits 'MV45AFZZ' and also 'MV45AFZB'.But i face the issue in both the exits.Please let me know if there are any means to solve this issue(as mentioned in case 3).
    Regards,
    S.Suba

    Many thanks for your answer. It help me to solve the issue.
    So applying note 738171, with transaction OVB5 (or VOFM, requirements->subsequent functions->Purch.requisitions) we create one new requirement, ie RV07A900, and then we apply the rule that if we have delivery or billing block, that is, VBAK-LIFSK or VBAK-FAKSK not empty, then we set an error with a code similar to this:
                da_sy-msgid = 'Z1'.    (message class)
                da_sy-msgno = '001'.  (message number)
                error_exception = true.
    and then the PR is not created.
    Regards.

  • Purchase requisition with reference to blocked sales order

    Hello,
    we are creating purchase requisitions (PR) manually with reference to a sales order (account assignment Z). When this sales order is blocked, we still can issue the purchase requistion.
    What can we do to avoid this? I think in 2 solutions:
    - use enhancement MEREQ001 to show error message when SO is blocked, so PR is not created. Is this possible?
    - create a release strategy for PR created in that plant (tr. OME6). The problem is that release strategy refers to an amount in the PO, and not to other factor, like SO blocked. Maybe in the former enhancement we can set the field EBAN-GSFRG to 'X'?
    Thanks for your help.

    Many thanks for your answer. It help me to solve the issue.
    So applying note 738171, with transaction OVB5 (or VOFM, requirements->subsequent functions->Purch.requisitions) we create one new requirement, ie RV07A900, and then we apply the rule that if we have delivery or billing block, that is, VBAK-LIFSK or VBAK-FAKSK not empty, then we set an error with a code similar to this:
                da_sy-msgid = 'Z1'.    (message class)
                da_sy-msgno = '001'.  (message number)
                error_exception = true.
    and then the PR is not created.
    Regards.

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

  • Val.Price for the requisition on the sales order

    Hi,
    I am creating automatically purchase requisition on the sales order with NLAG material type.
    My problem is system asking Val.Price for the requisition on the sales order. I don't want the this screen when sales order create.
    My Purchase Req. Doc Type = NB
    Field Selection key = NBB for the NB
    NBB Field Label >> Quantity and Price >> Price and price unit = Optional Entry
    Thank you
    Gulay Celik

    Hi Gulay,
    The error is coming because you have not maintained Accouting view of this material for teh plant, from where you want to procure/ship the material.
    Or even after you have maintained the Accouting view, Material price (Moving avegare price when price control is V must be Zero)
    Kindly check the master data records.
    This will resolve your issue.
    Regards,
    Dnyandeo H. Ainarkar

  • How to delete or activate the deletion flag for the sales order line item

    Hi All,
    I  have one Cust order & with referance to that cust order one production order is created . The production order user has done the Goods issue with 261 movement type  & GR wi 101 before 4 months back , & he has reverse  the GR  with 102 on todays date . but in materila master the  variable prize is maintain thats why it is showing  a differance in the cost .
    User want to delete the Production order as well as the custemer order From MDO4 , So we have make the Production order TECO & save , it is gone form the MD04 but the Custumer order still there . It is not allow us to cancell or reject . We have tried to maintain the reason for rejection but it showing the message that you can not activate the deletion flag for the order .
    Could you please Help me to find out the way how can i delete the custemer order ?
    Thanks In advance
    Regards
    Piyush

    W ehave Settele that order & then activate the deletion flag for the order & then cancel the sales order.

  • How to use a purchase condition in the sales order

    Hello,
    Customer would like to have a purchase "day-price" appearing in the pricing of the sales order. 
    I would suggest to write abap code (reading the correct PU condition record) in a condition base value routine that would be added in the customizing pricing procedure at SD side.
    Is there any "more standard" solution for this ? 
    Thanks,

    Hello,
    Here is the case in more detail :
    This question concerns a product that is just purchased, stored, and sold.  The purchase-price is based on a "day-price" that is maintained in a purchase condition record on a daily basis.  The sales-price should be that daily price with a markup in %. 
    So, in the sales order, this purchase condition record should be picked up with the material and the pricing date as key.  From that base price, a markup can be calculated in sales pricing. 
    I would suggest to use the field "condition base value" in the setup of the sales pricing procedure (Ref to IMG sales and distribution, pricing control, define and assign pricing procedures).  In that field a new routine could be entered that (with a select or function or Bapi) picks up the purchase condition record-value. 
    I would like to know if this would be a "correct" way of solving this requirement,  if there is no "more standard" solution,  if anyone has experience with a similar requirement and how you solved it ?
    Thanks,

  • How to delete a line item from the sales order

    Hi all,
    how to delete a line item from the sales order for which the production is already happened and it has been delivered. the production order status is DLV.
    Regards
    Kumar

    Hi
    U can do this in two ways one u can short close the order by entering Reason for rejection in VA02 at header level and if yr order is multiple line item order u can enter the reason for rejection in any of the line item which u don't want to deliver.
    This is called short close ( as the qty is not delivered fully).
    Thx.

  • "In FBL5N unable to view purchase order number and the sales order number"

    Hi,
    Below mentioned is the problem we are facing,
    In the Customer Line Item Display (FBL5N) it is vital for us to be able to view the customer's purchase order number as well as the sales order number for each billing document listed by customer.
    We need to be able to extract this information for each customer and import to an excel spread sheet for analysis, specifically for our larger customers that have over 500 plus lines.
    Kindly advise how to go about the same.
    Regards
    Harish

    Dear,
    Please also check note 152335. There, you will find a more detailed            
    explanation of the issue.                                                                               
    The only way to see some information regarding related PO-es in a Vendor       
    line items is a workaround. For example, it is possible to create              
    a substitution in order to fill in one of not currently used fields            
    like Reference, Text, etc.    
    I hope this helps You.
    mauri

  • Purchase orders manily against the sales orders

    My client do purchase orders manily against the sales orders... but to meet the minimumn purchase order quantity or value they club many sales orders in a single purchase order... now is there any way to track for what sales-order-item what purchase-order-item made?? (in SAP B1 2007 B PL7)

    Hi
    By Design ,SAP creates link between SO to PO when you create PO based on SO .
    Then you can use TargetDoc  which is PO  Number and can be seen in row level
    If it is disabled , you can enable it through form setting .
    I usually ask my user to start with SO . When they are ready to make purchase , they can click on purchase check box on SO and create PO based on SO . This way the link stay as B1design .
    The reason of this you can see the PO and (orrange arrow link) which can let you navigate your PO  from AR module .
    An other workaround  ,user defined field can be used at row level and manually link
    Hope this helps
    Bishal

  • 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

  • I am facing a problem in the sales order the purchase requistion no is not

    Hello SD Gurus,
    I am facing a prob in the sales order the purchase requistion is not coming, is there any config settings is required.
    In my bcness process after creating the SO automatically through wokflow the Purchase order will trigger.
    I have checked in the SO which is existing in the schedule line the purchase requistion is not showing.
    In the schedule line functionality is perfect.
    Other than this is it required more..............
    Gurus i am waiting for your reply.......................
    Regards,
    Kishore

    Hi kishore
    Firstly in VOV6 select the schedule line CS and check wheather in that schedule line the following data has been maintained or not
    Document type : NB
    Item category :    5( Third party)
    Account assignment category : X (  Account assignment )
    Secondly go to VOV7 and select the item category TAS and check the following data
    Automatic PO generation has been checked on or not
    Billing relevance should be F
    Regards
    Srinath

  • Enhance Event LIKP to also pass the Sales Order during Change & Delete

    Hi,
    Event/object LIKP is triggered when creating, changing or deleting a Delivery.
    We have workflow links in place, which call custom FM's when creating or changing the delivery. These FM's are able to populate tables during such events.
    However, after a delivery is deleted, there is no way to link it back to the Sales Order. Entries in table VBFA are deleted with the delivery deletion.
    As such, we'd like to enhance event/object LIKP to also store/pass the Sales Order to our custom FM.
    How do I enhance LIKP to do this? I know it's done in SW01 and I might need a new container, but I have no idea on how to do this. Please suggest.

    Bump ...

  • Can we delete the sales order?

    hi,
    can we delete the sales order?

    Use transaction code SARA for deletion of sales order but as every body said it is not recommended as it might affect the documents made against it and also the master data.
    So its better to reject the sales order.
    Regards
    Prashant

Maybe you are looking for