how to have a manual description + an id in SRMDOCP05 ?

[former_member198110]

i use standard LOIO SRM_DOC05 class :

When i create/upload a document using this standard feature, i have 2 attributes for this object : SRM_DOCUMENT_ID & SDOK_TITEL

Here : SDOK_TITEL = "DOC TEST COUCOU"

SRM_DOCUMENT_ID = "5 - 13.09.2016". I use a rule to get this filled automatically & get the unicity. i don't want/need unicity for the description which is Buz oriented

My issue/pb is when i save, SDOK_TITEL is replaced by the id coming from the rule ...  I don't understand this behavior.

"DOC TEST COUCOU" gets lost.

in the table, i find SDOK_TITEL = "5 - 13.09.2016"  ("DOC TEST COUCOU" was replaced) and i don't know where SRM_DOCUMENT_ID is stored / managed. i want/need to keep both information : the automatic ID for unicity. The description for the BUZ, without unicity.

This expected behavior works well for record objects. I don't understand this issue for "Document" object.

Thanks for any simple solutions / advices

Regards

[Pragya_Pande · Accepted solution]

Hi,

Are you using SCASEPS? This behavior is a standard behavior for documents in SCASEPS.

Check the classes used in service provider of this document element type. If it is RMPS**then you are using Public Sector flavor where this is a standard behavior.

Best Regards,

Pragya

[former_member198110 · Accepted solution]

Hi Pragya

yes, i'm using scaseps.

and i'm using standard LOIO/PHIO classes "05"

If this is standard behavior, i don't understand why we have 2 fields (short description & unique id) in the user screen while only one value is saved ...

why "short description" value is lost / not saved somewhere ?

regards

[ivan_shadrin · Accepted solution]

I didn't know that you are using SCASEPS 😉

I saw the SRM_DOC05 in your first post and decied that you're working in ORGANIZER in standard RMS_ID S_RMS_DEMO.

That's the reason why I couldn't reproduce your issue.

SCASEPS has different implementation of service providers and completely different customization.

I've tried to create a document in SCASEPS using the standard element Document.

It is based on the element type RM_PS_SPS_DOCUMENT and Logical object class RPS_DOC02.

As you can see, the standard attribute Description is hidden and therefore should be filled automatically. I think it is implemented in the service provider of the RM_PS_SPS_DOCUMENT.

Perhaps, you have created your own element type and assigned a SRM_DOC05 via the connection parameter. And, as we can see, SRM_DOC05 is incompatible with this service provider.

[former_member198110 · Accepted solution]

i love you. 🙂

This is indeed the correct explanation of what was done in my system ...  🙂

i followed your advice & created a Z attribute for the Buz description, added to the copy of RPS_DOC02 instead of SRM_DOC05. it works now the way i need & i understood the system behavior 🙂

Thanks a lot for your help.

Regards

Thierry

[ivan_shadrin]

So, the reason of this issue is described in my previous post.

If you want to provide the user with the possibility to enter the free text description, you should do the following:

1) go to the DMWB and create a copy of the standard object RPS_DOC02, RPS_DOCP02 and so on. Please refer the documentation (see the link in another your question).

It is strongly recommended to use this Info object because it is compatible with the service provider implementation that you use in the scaseps.

2) In the SRMREGEDIT create a new element type

In connection parameters specify the logical class you have created in the step 1.

3) Add in the logical (or physical) object custom attributes. And let your end-users enjoy SAP Records Management 🙂

[ivan_shadrin]

Hi,

I've tried to reproduce in my system the issue you've described, but unsuccessfully.

Of course, I've used the same info object classes and out-of-the-box customizing provided by SAP in S_RMS_DEMO.

In my test system description doesn't change automatically even if I give the same description for two different documents.

Have you ensured that there are no custom developments in your system which could influence the description assignment?

For example, BAdI implementations (especially CHANGE_ATTR_C), or extended Service providers and so on...

[former_member198110]

Hi Ivan

Thanks for your feedback. i'm going to check your point as there is indeed a big team here ...

I'm very interested in your test. could you provide with the followings details please ?

- did you use SRMDOCP05 or P04 ?

- screenshot of the attributes you entered when creating the document (equivalent to mine)

- screenshot of the created entry in SRMDOCP05 once saved (equivalent to mine)

in which field of the table were saved the "short description" & "unique ID" ?

in my system, "Short description" entered is replaced by "Unique Id" value and saved in "Descript" field. I don't understand where should be stored the "Unique ID" value ..

Thanks a lot for your help.

Regards

Thierry

[ivan_shadrin]

Well, I've created several documents.

Let's consider two last.

Both of them based on Logical Class SRM_DOC05 and corresponding physical class SRM_DOCP05.

During the logical and physical classes activation a plenty of different tables are being created.

The most convinient way to find them is to open the class properties, copy the package name (see in the picture below) and then browse the ABAP tables in that package in the SE80.

Then you should find the table for the attributes of the object.

In our example the "Unique ID" attribute is stored in SRMPHPR05.

Here are the unique ID's of the four documents I've created when trying to reproduce your issue:

The document descriptions could be found in SRMDOCP05.

The tables are different because the description is a standard attribute 'DESCRIPTION' which always stored in the header table and the "Unique ID" is a custom attribute 'SRM_DOCUMENT_ID' which by default is stored in the special table for attributes.

More details here.