Travel Expense Attachments

[Former Member]

We are interested in using the file attachments functionality for Travel Expense Reports through ESS. We want to set up the attachments as Business Objects so that creation / update / deletion can be controlled by security roles. We have searched for documentation on the subject but have had very limited success. Has anyone else done this? What are the correct Business Objects? Thanks.

[former_member131723 · Accepted solution]

Hi Grover

Its business object BUS2089, you should also check the customizing in feature TRVPA via transaction PE03  - if OAA is set to "0" then you will only see attachments to a trip (BUS2089) and if it is set to "1" then you will see both attachments to a trip and also stored business documents (TRAVEL)..however this is all relevant on a more basic point, I have not seen any scenario that controls editing of attachments by security based authorization roles

Just on the attachment customising itself ..note: there are 2 kinds of documents which can be shown.
Document types for attachments to a trip are shown due to the use of BUS2089. Document types as archived business documents are shown due to the use of TRAVEL.
Attachments  > BUS2089, Business documents   > TRAVEL.

See also notes 530792  and  904711 as the documentation may help here also.

Please also note that there are some minimum BP requirements and also that certain functionality is only possible in WD ABAP landscape as there is less possibility for display of archived and scanned documents in Java portal. (There is some additional functionality coming with EHP6 also for WDA)

http://help.sap.com/erp2005_ehp_04/helpdata/en/5d/eecf6d3832433ea4d292e57d925e10/frameset.htm

So to sum up, you need to check your customizing for BUS2089 consider your workflow requirements and then decide on the type of attachment you want!

Hope it helps

Sally

P.S..... there are some other threads with similar info on SDN around this subject over the past few year!

of attachment you want!

[Former Member]

Thanks Sally!