Customizing of GOS (Generic Object Service) working for SAPGUI but not for Fiori

[benoit-schmid]

Good Afternoon,

I have customized the GOS by setting PCATTA_CREA, NOTE_CREA & URL_CREA to inactive table SGOSCUST.

These parameters settings works for GAPGUI accesses: The Attachement, Notes & URL are inactivated for GOS.

But, with Fiori accesses, these customizing are ignored because it is possible to create a GOS Attachement, Note or URL.

Why is Fiori ignoring this configuration?
How can I configure this for for Fiori?

Have a nice day.

[Sandra_Rossi]

Which Fiori App?

[Jocelyn_Dart · Accepted solution]

Generally we use Harmonized Document Management in S/4HANA which covers you for GOS, DMS, and other document frameworks. Many SAP Fiori apps are now using this approach via the F1243 Attachment Service app. This is the current documentation link for the latest release of HDM: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/36802406aebb4b96b1598246e1d316ee/bc275e43f1b043cc8f9...  

This is the link to the Attachment Service app - you can see in Related Apps many of the apps using this service. https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/detail/Apps('F1243')/S28OP 

Essentially HDM solves the old GUI problem of competing document frameworks where attachments showed up in different places at different times which was very confusing for users. Now they can all be seen by using HDM. 

[benoit-schmid · Accepted solution]

Good Morning Jocelyn,

Thanks for your answer.
Your are telling me that I should use the HDM customizing to deactivate this feature.

After reading your HDM documentation, I have test the effect.
With the transaction hdm_cust, I have deactivated each Attachment Object Type.

Then I have used the FI Manage Entry Tile (/sap/bc/ui2/flp#AccountingDocument-manage).
But the upload facility that uses the GOS is still activated.

Basically, the HDM does not work for this tile.
Which other options do i have to deactivate this upload?

Have a nice day.

[Sandra_Rossi · Accepted solution]

@benoit-schmid FYI your comment is truncated.

[benoit-schmid · Accepted solution]

Good Afternoon,

You were right because HDM is the way to go to configure attachments in Fiori.
After our Go Live from ECC 6.07 to S4 2021, I started to notice the following points.

(1) New attachments started to be created in the DMS.
(2) New attachments started to be created in GOS.
(3) New attachments were added in ArchiveLink as intended.

(1) was due to the fact that HDM had not been configured.
DMS is the default for HDM. Therefore (1) has been solved by configuring HDM.
First Fiori Experts said that ArchiveLink upload was not possible through Fiori.
But it turned that it is possible with HDM.

Concerning (2), we were disappointed because we had deactivated GOS upload (SGOSCUST).
This configuration is used by GUI transactions.
But it is ignored by lots of Fiori Apps that do not support HDM.
These apps sometimes uses GOS by default.
But they ignore SAP official customizing for GOS.
Contacting SAP support was quite painful because they were saying that Attachment Services does not use GOS although it does.
For example, the development support teams answered the following regarding documents stored with the GOS from a Fiori App:
"The customization for GOS functionalities does not affect Fiori as it use a different services that it is not from GOS"
"Design in Fiori is different form the GUI options and the customizing is not always recognized."

Then, we investigated what we could change by configuring HDM.
Unfortunately we discovered that not all Fiori Apps support HDM.
We also discovered that SAP released notes to support "Custom HDM".
With Custom HDM more Fiori Apps support HDM.
But there are remaining Fiori Apps that do not support HDM or Custom HDM.

Looking at DMS & GOS link tables, it turned out that we were using attachments for the following objects in our S4 2021.

- BUT000/BUS1006 (Business Partners)
- LFA1 (Suppliers)
- LFB1 (Supplier Company Code)
- BKPF (Journal Entries)
- BUS2081 (Supplier Invoices)
- VBRK (Billing Documents)
- BUS2012 (Purchase Orders)
- BUS0033 (Fund Centers)
- BUS0034 (Funds)

BUT000/BUS1006, LFA1 & LFB1 could be configured with hdm_cust.
With HDM, DMS is now configured as restricted to access old DMS documents and ArchiveLink is configured as active.

BKPF, BUS2081, VBRK and BUS2012 could be configured with hdm_cust after activating Custom HDM.
For these BOR Objects, Attachment Services without HDM, stored the documents in the GOS, by default.
With HDM, GOS is now configured to restricted to access old GOS document and ArchiveLink is active.

Even after having activated CUSTOM HDM, BUS0033 & BUS0034 were still problematic because the associated Fiori App stored document only in GOS.
As these Objects are used by Public Sector, I contacted EA-PS & CA_DMS support.
I asked them if they would agree to adapt their Fiori Apps for Custom HDM.
The good news is that they said yes and released a few SAP Notes to achieve it.

Therefore, with our current used Fiori Apps, we are able to configure a central and unique technology (ArchiveLink) to be used for all our attachements.
But we may face future problems, in the case we would start to use new Fiori App that would not support HDM or Custom HDM.

The second good point with HDM, is that our old GOS and DMS documents are still available for our users.

Have a nice day.

[benoit-schmid]

Good Morning,

I have performed the following tests:

1. From SAPGUI, use transaction FB03.
I have not succeeded to upload a new Document with GOS has it is deactivated.

2. From Fiori Launchpad, I have used Manage Journal Entry (AccountingDocument-manage)
---
Manage Journal Entry (AccountingDocument-manage)
-> Provide the Journal Entry
--> Go
---> Click on the Journal Entry
----> Manage Journal Entries
-----> Click on Attachments
------> Click on Edit
-------> Click on Upload
--------> Provide the PDF File
---------> A new document is added using GOS
---

Does this describes enough for you to understand?

Have a nice day.