To prevent Users to delete an attachment in a Sales order

Dear All,
I have attched a word doc. in a Sales order.I made the settings such that Users cannot edit/change the file(file unchangeable/changeable by the author).But there is an option where users can delete it. where can I / what settings it requires to restrict the users from deleting it.
helpful answers will be rewarded.
Thankx
Krishna chaitanya

Dear,
To attach a word doc/excel sheet etc. to a sales order, so that whenever we open that particular Sales order we can able to see the info. saved as attachment.
va02>system>user profile>own data>parameters--->here we need to enter the particular parameter ID......."SD_SWU_ACTIVE"...and the parameter value is "X".
The parameter mentioned above will activate workflow box in va02 nad va03 only.
save it...U will now can see an ICON--"Services for object"...just below the command box...or else goto SYSYTEM-services for object.
reward if helpful
Krishna chaitanya

Similar Messages

Prevent user from deleting rows from all tables in his own schema

Hi,
How can I prevent user from deleting rows in all tables in his own schema.
I want the user to not able to delete rows from any existing or new tables that might be added in the future.
The user does not have the "DELETE ANY TABLE" system privilege.
Please advise.
Thanks.

Nowadays, I'd also avoid triggers (if possible).
Sometimes, when I daydream, I'm rewriting a few applications that I've contributed to as a newbie, and I'm very ashamed of it nowadays.
From what I've experienced, in retrospective, the emphasis on teaching 'Oracle stuff' has been lying far too much on PL/SQL row-by-row oriented processing instead of letting Oracle 'crunch' sets at once.
Most of my debugging hours ended up in discovering one or more database triggers 'doing stuff automagically'.
Another nice blogpost: http://rwijk.blogspot.com/2007/09/database-triggers-are-evil.html
Regarding OP's question:
I would just rethink/reconsider this requirement completely.
Correctly implementing privileges and roles seems the best way to go, yes.
Triggers? Nah...
pre-post-edit, noticed thread got updated just before posting
Don't know what you mean with 'namedropping', but I think it's legitimate to point other readers to interesting Oracle related opinions/articles that do have a technical background and lots of interesting examples.
post dreaded OTN outage edit (from here)
Again: I would just rethink/reconsider this requirement completely.
Both trigger/vpd are being used to hide a design flaw here.

Prevent user from deleting someone else data

I have a table
create table T(
infoID number primary key,
info varchar2(4000),
user varchar2(1)
and users a,b,c with object priveleges on table T.
What is the best way to prevent user from deleting someone else data?
1. Create a view for each user to interacat with ( where user='a') and revoke privileges from table T.
2. Use procedures or trigers to catch a bad user.
3. ?

Leo is certainly correct that VPD will solve the issue you have described. however another option also exists without the need to create a separate view for each user (as you described) or the use of VPD, the option would be to do something like the following.
create user ownera identified by ownera;
create user usera identified by usera;
create user userb identified by userb;
create user userc identified by userc;
grant connect, resource to ownera;
grant create view to ownera;
grant connect to usera, userb, userc;
conn ownera/ownera
create table mytable ( id number primary key,
userid varchar2(8) not null, mod_date date not null, text varchar2 (100));
create sequence mytable_seq;
create or replace trigger biu_mytable_trg
before insert or update on mytable
for each row
begin
     select mytable_seq.nextval into :new.id from dual;
     :new.userid := user;
     :new.mod_date := sysdate;
end;
create or replace view v_mytable as
select * from mytable where userid=user;
grant select, insert, update, delete on v_mytable to usera, userb, userc;
try inserting and selecting as the various userX users.
Good luck.

Hi All, We are in to Release 11.5.10.2.There is a specific requirement to Prevent users from creating Manual Sales Orders in oracle and yet users should be able to book the Sales Orders Imported from CRM system into Orcale.Please advise.

Hi All, We are in to Release 11.5.10.2.There is a specific requirement to Prevent users from creating Manual Sales Orders in Oracle and yet users should be able to book the Sales Orders Imported from CRM system into Orcale.Please advise.

Thanks for your advise.
However, I missed to mention that we have two set of users One is for Finished Goods and another for Spares.
Only Spares users need to be prevented from creating Direct/Manual Sales Orders in Oracle.
As you suggested, if this will be done at Form level, that may Disallow FG users also to create Manula Sales Orders which should not be the case.
Further, I tried to test one scenario through Processing Constraints but it did not work.
Application
OM
Validation Type
Entity
Temp
Short Name
TBL
Validation Semantics
Created By
Equal To
User(Myself)
Processing Cosntraint
Application
OM
Entity
Order Header
Constraint
Operation
User Action
Create
Not Allowed
Conditions
Group
Scope
Validation Entity
Record Set
Validation Template
101
Any
Order Header
Order
Above Created
Please advise.

Problem with attaching file to Sales Order

Hello,
In my company we have the possibility to attach files to sales orders, e.g. pdf files with the printing details.
These files are added by the GUI user, this works fine.
Now we have an extra order creation stream in which a pdf file has to be added to the SO without user interaction.
I found a helpful link ( /people/rammanohar.tiwari/blog/2005/10/10/generic-object-services-gos--in-background )
This program creates URL links with no problem, but the file generation is not implemented yet.
I tried to add the file functions to his sample report but still have one problem. The file is uploaded, but not reported as a PDF file in sap. If I select the created attachment SAP allows only the saving of the attachment. After saving the created file is a good PDF file, it opens with PDF-viewers.
Why does SAP not know this is a PDF file and report it as such (and open the pdf viewer when selected).
Thanks, Frank.
source-code:
REPORT zzfb_brc                                .
* Report Z_RMTIWARI_ATTACH_DOC_TO_BO
* Written By : Ram Manohar Tiwari
* Function   : We need to maintain links between Business Object and
*              the attachment.Attachment document is basiclally a
*              business object of type 'MESSAGE'.In order to maintain
*              links, first the attachment will be crated as Business
*              Object of type 'MESSAGE' using Message.Create method.
*              Need to check if we can also use FM
*              'SO_DOC_INSERT_WITH_ORIG_API1' or SO_OBJECT_INSERT rather
*              than using Message.Create method.
* I took this program and removed all the parts for adding URL's and
* notes.
* Include for BO macros
INCLUDE : <cntn01>.
* Load class.
CLASS cl_binary_relation DEFINITION LOAD.
CLASS cl_obl_object      DEFINITION LOAD.
PARAMETERS:
* Object_a
   p_botype LIKE obl_s_pbor-typeid DEFAULT 'BUS2032',    "SO
   p_bo_id LIKE obl_s_pbor-instid DEFAULT '0000757830', "example number
* Object_b
   p_docty LIKE obl_s_pbor-typeid DEFAULT 'MESSAGE' NO-DISPLAY,
   p_msgtyp LIKE sofm-doctp        DEFAULT 'EXT'     NO-DISPLAY,
* Relationship
   p_reltyp LIKE mdoblrel-reltype DEFAULT 'ATTA'.
TYPES: BEGIN OF ty_message_key,
        foltp     TYPE so_fol_tp,
        folyr     TYPE so_fol_yr,
        folno     TYPE so_fol_no,
        doctp     TYPE so_doc_tp,
        docyr     TYPE so_doc_yr,
        docno     TYPE so_doc_no,
        fortp     TYPE so_for_tp,
        foryr     TYPE so_for_yr,
        forno     TYPE so_for_no,
       END OF ty_message_key.
DATA : lv_message_key TYPE ty_message_key.
DATA : lo_message TYPE swc_object.
DATA : lt_doc_content TYPE STANDARD TABLE OF soli-line,
       ls_doc_content TYPE soli-line.
* Create an initial instance of BO 'MESSAGE' - to call the
* instance-independent method 'Create'.
swc_create_object lo_message 'MESSAGE' lv_message_key.
* Upload the pdf file, for now from the frontend, in the future from
* the server.
DATA:
* dsn(40) TYPE C VALUE '/usr/sap/trans/convert/1.pdf', "server location
l_lines TYPE i. "filelenght
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
    filename   = 'c:t1.pdf'
    filetype   = 'BIN'
IMPORTING
    filelength = l_lines
TABLES
    data_tab   = lt_doc_content.
* no exceptions, the file is there in this example
break brouwersf.
** the coding for the server input, for later
*OPEN DATASET dsn FOR INPUT IN BINARY MODE.
*IF sy-subrc <> 0.
* EXIT.
*ENDIF.
*READ DATASET dsn INTO ls_doc_content.
*WHILE sy-subrc EQ 0.
* APPEND ls_doc_content TO lt_doc_content.
* READ DATASET dsn INTO ls_doc_content.
*ENDWHILE.
*CLEAR ls_doc_content.
*CLOSE DATASET dsn.
* define container to pass the parameter values to the method call
* in next step.
swc_container lt_message_container.
* Populate container with parameters for method
swc_set_element lt_message_container 'DOCUMENTTITLE' 'Title'.
swc_set_element lt_message_container 'DOCUMENTLANGU' 'E'.
swc_set_element lt_message_container 'NO_DIALOG'     'X'.
swc_set_element lt_message_container 'DOCUMENTNAME' p_docty.
swc_set_element lt_message_container 'DOCUMENTTYPE' p_msgtyp.
swc_set_element lt_message_container 'DocumentSize'    l_lines.
swc_set_element lt_message_container 'DocumentContent' lt_doc_content.
swc_call_method lo_message 'CREATE' lt_message_container.
* Refresh to get the reference of create 'MESSAGE' object for attachment
swc_refresh_object lo_message.
* Get Key of new object
swc_get_object_key lo_message lv_message_key.
* Now we have attachment as a business object instance. We can now
* attach it to our main business object instance.
* Create main BO object_a
DATA: lo_is_object_a TYPE sibflporb.
lo_is_object_a-instid = p_bo_id.
lo_is_object_a-typeid = p_botype.
lo_is_object_a-catid = 'BO'.
* Create attachment BO object_b
DATA: lo_is_object_b TYPE sibflporb.
lo_is_object_b-instid = lv_message_key.
lo_is_object_b-typeid = p_docty.
lo_is_object_b-catid = 'BO'.
*TRY.
CALL METHOD cl_binary_relation=>create_link
EXPORTING
    is_object_a = lo_is_object_a
    is_object_b = lo_is_object_b
    ip_reltype = p_reltyp.
* Check if everything OK...who cares!!
COMMIT WORK.

Hi,
Welcome to the SDN Forums!!!
You need to supply the PC file extension in the container element 'DOCUMENTTYPE'.
swc_set_element lt_message_container 'DOCUMENTTYPE' p_msgtyp.
In your case change the above statement as below:
swc_set_element lt_message_container 'DOCUMENTTYPE' 'pdf'.
<b>OR</b> change the default value of p_msgtyp to 'PDF'.
Cheers,
Ramki Maley.
Please reward points if the answer is helpful.
For info on awarding points click on this link: https://www.sdn.sap.com/sdn/index.sdn?page=crp_help.htm
Message was edited by: Ramki Maley

How to delete header condtion line of sales order by BAPI

Hi,
I want to delete the condtion line of sales order header using BAPI "BAPI_SALESORDER_CHANGE",
it is work well in item level condition type, but it is not work for header condition type. show error message "missing item number" since of pass item number "000000" for header condition line.
Below is reference source code, thanks in advance.
*& Report ZTEST_BAPI_SO_DELETECONDLINE
*& Sample program to call BAPI_SALESODRER_CHANGE to
*& delete condition line of so line item
REPORT ZTEST_BAPI_SO_DELETECONDLINE.
***--- Structures for create BAPI
DATA: SALESDOCUMENT LIKE BAPIVBELN-VBELN.
DATA: ORDER_HEADER_INX LIKE BAPISDH1X,
      BEHAVE_WHEN_ERROR LIKE BAPIFLAG-BAPIFLAG,
      SIMULATION LIKE BAPIFLAG-BAPIFLAG.
DATA: BEGIN OF ORDER_ITEM_IN OCCURS 2.
        INCLUDE STRUCTURE BAPISDITM.
DATA: END OF ORDER_ITEM_IN.
DATA: BEGIN OF ORDER_ITEM_INX OCCURS 2.
        INCLUDE STRUCTURE BAPISDITMX.
DATA: END OF ORDER_ITEM_INX.
DATA: BEGIN OF SCHEDULE_LINES OCCURS 2.
        INCLUDE STRUCTURE BAPISCHDL.
DATA: END OF SCHEDULE_LINES.
DATA: BEGIN OF SCHEDULE_LINESX OCCURS 2.
        INCLUDE STRUCTURE BAPISCHDLX.
DATA: END OF SCHEDULE_LINESX.
DATA: BEGIN OF ORDER_CFGS_REF OCCURS 2.
        INCLUDE STRUCTURE BAPICUCFG.
DATA: END OF ORDER_CFGS_REF.
DATA: BEGIN OF ORDER_CFGS_INST OCCURS 2.
        INCLUDE STRUCTURE BAPICUINS.
DATA: END OF ORDER_CFGS_INST.
DATA: BEGIN OF ORDER_CFGS_VALUE OCCURS 2.
        INCLUDE STRUCTURE BAPICUVAL.
DATA: END OF ORDER_CFGS_VALUE.
DATA: BEGIN OF CONDITIONS_IN OCCURS 2.
        INCLUDE STRUCTURE BAPICOND.
DATA: END OF CONDITIONS_IN.
DATA: BEGIN OF CONDITIONS_INX OCCURS 2.
        INCLUDE STRUCTURE BAPICONDX.
DATA: END OF CONDITIONS_INX.
DATA: BEGIN OF EXTENSIONIN OCCURS 2.
        INCLUDE STRUCTURE BAPIPAREX.
DATA: END OF EXTENSIONIN.
DATA: BEGIN OF RETURN OCCURS 2.
        INCLUDE STRUCTURE BAPIRET2.
DATA: END OF RETURN.
DATA: TMP_POSNR LIKE VBAP-POSNR,
      L_KNUMV    LIKE VBAK-KNUMV,
      L_KSCHL    LIKE KONV-KSCHL,
      L_STUNR    LIKE KONV-STUNR,
      L_ZAEHK    LIKE KONV-ZAEHK.
***--- Selection
PARAMETERS: P_VBELN LIKE VBAK-VBELN OBLIGATORY MEMORY ID AUN DEFAULT '7000510', "'0001007443', " SO
            P_POSNR LIKE VBAP-POSNR OBLIGATORY DEFAULT '000000' , " so item
            P_CONDN LIKE KONV-KSCHL DEFAULT 'ZOSP',    " condition type
            P_CONDI LIKE KONV-ZAEHK DEFAULT '01',      " Condition item number
            P_TEST AS CHECKBOX DEFAULT 'X'.             " test mode
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      INPUT         = P_VBELN
    IMPORTING
      OUTPUT        = P_VBELN.
CLEAR: L_KNUMV.
SELECT SINGLE KNUMV INTO L_KNUMV
FROM VBAK
WHERE VBELN = P_VBELN.
IF SY-SUBRC = 0.
    CLEAR: L_KSCHL,L_ZAEHK,L_STUNR.
    SELECT SINGLE KSCHL ZAEHK STUNR INTO (L_KSCHL, L_ZAEHK, L_STUNR)
    FROM KONV
    WHERE KNUMV = L_KNUMV
      AND KPOSN = P_POSNR
      AND ZAEHK = P_CONDI
      AND KSCHL = P_CONDN.
    IF SY-SUBRC <> 0.
      WRITE:/ 'Condition type or condition item is not exist.'.
      EXIT.
    ENDIF.
ELSE.
    WRITE:/ 'Sales order number is not exist'.
    EXIT.
ENDIF.
IF L_ZAEHK IS INITIAL.
      WRITE:/ 'Condition type or condition item is not exist.'.
      EXIT.
ENDIF.
SALESDOCUMENT = P_VBELN.     " Sales order number
ORDER_HEADER_INX-UPDATEFLAG = 'U'.   "U = change sales order
***Item Data
ORDER_ITEM_IN-ITM_NUMBER = P_POSNR.
APPEND ORDER_ITEM_IN.
ORDER_ITEM_INX-UPDATEFLAG = 'U'.   "I = add, U= update, D=delete
ORDER_ITEM_INX-ITM_NUMBER = P_POSNR.
APPEND ORDER_ITEM_INX.
***--- Begin delete a condition line
***--- Make sure to use update flag 'D'. Here I = add, U= update, D=delete
CLEAR: CONDITIONS_IN,CONDITIONS_INX.
REFRESH: CONDITIONS_IN,CONDITIONS_INX.
CONDITIONS_IN-ITM_NUMBER = P_POSNR.
CONDITIONS_IN-COND_ST_NO = L_STUNR.
CONDITIONS_IN-COND_COUNT = L_ZAEHK.
CONDITIONS_IN-COND_TYPE = L_KSCHL.
APPEND CONDITIONS_IN.
CONDITIONS_INX-UPDATEFLAG = 'D'.
CONDITIONS_INX-ITM_NUMBER = P_POSNR.
CONDITIONS_INX-COND_ST_NO = L_STUNR.
CONDITIONS_INX-COND_COUNT = L_ZAEHK.
CONDITIONS_INX-COND_TYPE   = L_KSCHL.
APPEND CONDITIONS_INX.
***--- End delete a condition line
BEHAVE_WHEN_ERROR = 'P'.
SIMULATION = P_TEST.   " Test mode or not
"=== call BAPI
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
    SALESDOCUMENT               = SALESDOCUMENT
    ORDER_HEADER_INX            = ORDER_HEADER_INX
    LOGIC_SWITCH                = '    U'
TABLES
    RETURN                      = RETURN
    ORDER_ITEM_IN               = ORDER_ITEM_IN
    ORDER_ITEM_INX              = ORDER_ITEM_INX
    CONDITIONS_IN               = CONDITIONS_IN
    CONDITIONS_INX              = CONDITIONS_INX .
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
WRITE: / 'Return code =', SY-SUBRC.
SKIP 1.
LOOP AT RETURN.
WRITE: / RETURN-MESSAGE.
ENDLOOP.
Edited by: hank jiang on May 21, 2010 5:07 AM
Edited by: hank jiang on May 21, 2010 5:25 AM
Edited by: hank jiang on May 21, 2010 5:27 AM

SALESDOCUMENT = P_VBELN.     "Sales order number
ORDER_HEADER_INX-UPDATEFLAG = 'U'.   "U = change sales order
ORDER_ITEM_IN-ITM_NUMBER = P_POSNR.
APPEND ORDER_ITEM_IN.
ORDER_ITEM_INX-UPDATEFLAG = 'U'.   "I = add, U= update, D=delete
ORDER_ITEM_INX-ITM_NUMBER = P_POSNR.
APPEND ORDER_ITEM_INX.
"Begin delete a condition line
"Make sure to use update flag 'D'. Here I = add, U= update, D=delete
CLEAR: CONDITIONS_IN,CONDITIONS_INX.
REFRESH: CONDITIONS_IN,CONDITIONS_INX.
CONDITIONS_IN-ITM_NUMBER = P_POSNR.
CONDITIONS_IN-COND_ST_NO = L_STUNR.
CONDITIONS_IN-COND_COUNT = L_ZAEHK.
CONDITIONS_IN-COND_TYPE = L_KSCHL.
APPEND CONDITIONS_IN.
CONDITIONS_INX-UPDATEFLAG = 'D'.
CONDITIONS_INX-ITM_NUMBER = P_POSNR.
CONDITIONS_INX-COND_ST_NO = L_STUNR.
CONDITIONS_INX-COND_COUNT = L_ZAEHK.
CONDITIONS_INX-COND_TYPE   = L_KSCHL.
APPEND CONDITIONS_INX.
"End delete a condition line
BEHAVE_WHEN_ERROR = 'P'.
SIMULATION = P_TEST.   " Test mode or not
"=== call BAPI
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
    SALESDOCUMENT               = SALESDOCUMENT
    ORDER_HEADER_INX            = ORDER_HEADER_INX
    LOGIC_SWITCH                = '    U'
TABLES
    RETURN                      = RETURN
    ORDER_ITEM_IN               = ORDER_ITEM_IN
    ORDER_ITEM_INX              = ORDER_ITEM_INX
    CONDITIONS_IN               = CONDITIONS_IN
    CONDITIONS_INX              = CONDITIONS_INX .
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
WRITE: / 'Return code =', SY-SUBRC.
SKIP 1.
LOOP AT RETURN.
WRITE: / RETURN-MESSAGE.
ENDLOOP.

Delete the line item in sales order in VA01/VA02 when the quantity is modif

Hi SAP,
I have requirement to delete a line item in sales order.Please suggest me to do the same.
THe scenarios is , we are inserting a free good line item based on some condition and quantity, If the quantity is modified the free good line item inserted needs to be deleted.
Waiting for your responce
Thanks,
Billa
Moderator message : Spec dumping is not allowed,search for available information. Thread locked.
Edited by: Vinod Kumar on Nov 14, 2011 1:54 PM

Hi,
Can you also check the SALES LINE.
Sales line is the combination of SALES ORGANISATION + DISTRIBTION CHANNEL +PLANT.
Hope it was not maintained.
Transaction code : OVX6
PATH: IMG->ENTERPRISE STRCTRE->ASSIGNMENT>SALES AND DISTRIBTION->ASSIGN SALES ORG- DISTRIBTION-PLANT.
please revert if the error still exists.
santosh

User exit to copy the data from sales order to billing document

hi everyone,
Is there an user exit to copy the data from sales order to billing document?
Regards
Prabudh

hi
copy control would be the better option to choose.. but still u can a give a search in list below and opt for the right one..Refer to the link below..
http://www.planetsap.com/Userexit_List.htm
User exits for Sales order
1USEREXIT_DELETE_DOCUMENT
2USEREXIT_FIELD_MODIFICATION
3.USEREXIT_MOVE_FIELD_TO_VBAK
4.USEREXIT_NUMBER_RANGE
5.USEREXIT_SAVE_DOCUMENT
User exits for billing
1.USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
2.USEREXIT_ACCOUNT_PREP_KOMPCV
3USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
4USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB
5.USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
Reward if Useful
Thanx & Regards..
Naren..

FM to delete / clear payment block in Sales Order

Hi,
Could any one tell me the FM to delete payment block in the Sales Order in the Billing Plan. My requirement is, on any given date, if the payment is due, remove the payment block for the sales order. The Payment block value is in FPLT-FAKSP field. But I could not find any FM to change the value of FAKSP to SPACE.
Thanks
Sai Prasad R

Check transaction code VBSY ( report ROGBILLS )

VL01N user exit to copy pricing conditions from sales order

Does anyone know which user exit could be used to copy sales order line item conditions to delivery note conditions screen.
The sales order screen is SAPLV69A field KOMV-KSCHL
The delivery note screen is SAPLV69A field KOMV-KSCHL
Thanks

Hi,
Just goto include - LV69AFZZ
And Check ..
userexit_pricing_check - USEREXIT_PRICING_CHECK
Thanks

Attached documents in sales order disappears in Invoice

Hi All,
I attach some documents in change mode of sales order and when i see the Invoice it disappears. Can someone help me what settings or which object if activated can carry the attached documents from sales order to Invoice.
Thanks.....

Hi,
Please refer to this link. A similar situation has been discussed in this link.
File to copied from one tcode to another tcode
Let me know if you are still having issues with this.
Regards,
Rohan Gudavalli

Delete or insert item in Sales Order and Purchase Order will update as well

Hi,
Is anyone got the program code that when i delete or insert item in Sales Order and the back to back Purchase Order will do the same action.
Please help.
Regards,
Anna

Hi,
I guess u can try the following,
Once the SO is updated, check with a SQL query if there are any target docs for that SO then, if there are any target docs u have to check for the item thats updated and then update ur PO using DI.
Hope it helps,
Vasu Natari.

User exit for setting tax indicator in Sale order

Hi All,
I want to know if there is a way (user exit) that could look at the Sales Order Type , particular Item Pricing Condition and Ship-to party State and set the materialu2019s tax classification (VBAP/TAXM1) to u201C0u201D (Exempt) ?
Thanks in Advance!
Sonali.

Hi Ramesh,
I have put the code in the user exit, and I am able to set the tax classification indicator but I have a problem... Before setting the indicator I need to check for the Usage code of the line item (This code I am using instead of checking the Pricing condition) . I am able to read all the values of line item in VBAP structure in the user exit except for the first time this user exit is hit as soon as a line item is entered it is not picking up the Usage code. That field is blank.
But if add another line item and go into the user exit I can see the previous line item Usage code in XVBPA table.
Do you have any idea why usage code is missing in VBAP structure in the user exit or is there any other table or structure where I can get the usage code?
Thanks in Advance!
Sonali.

SAP won't let me delete an item from a sale order!

I am trying to delete an item from a sale order but i get this message
"A production order already exists for item 000030
Message no. V1603"

What was the item category of material??also what was the movement type assigned??
If already some production order exists with this line item then ask your PP guy to come out of this...(first you need to take necessary action on Production order--then you can delete line item at sales order level)
Phanikumar

Prevent user from deleting PO

1. Is there a way to prevent the user from deleting the PO item if GR/SA had been done for service PO. (Just like how the system behave for material PO - Message 06 115).
2. We also want to prevent the user from deleting the PO item if GR/SA and IR had been done for service and also material.
Please advice. Thank You.

1.Is System allowiing the user to DO ?
2.User Deleting only Items ?
if So then u have to activate User Exits or BADIs.
Regards
Peram

To prevent Users to delete an attachment in a Sales order

Similar Messages

Maybe you are looking for