Change version not creates some times in GOA

[Former Member]

Hello All

there is one piece of field in GOA will not create a change version.

as i know any piece of data changes will create a new versiona and workflow will get triggered.

i wanted to know which field changes will not create a Change version in GOA ?

any ppointers -->docuemnts ,, etc .

muthu

[Former Member · Accepted solution]

Do you mean "Change Version" (version type C) or a new version completely?

The new version creation (or not) is dictated by table BBPD_COMP_FIELDS.

[Former Member · Accepted solution]

yes jay.

some times change version was not created and approval also not trigered .

so i wanted to see what are the field changes in GOA will not create a change version.

should i look only CDI ?

i could not see any any docuemnts. for eg. if i attach any change version must create right?

i dont see any fields for attachment or notes ...text..

versions created. but logs are captured but i donot see attachemnts,

muthu

[Former Member · Accepted solution]

some times change version was not created and approval also not trigered .

From BBP_PD, do you see the new historical version at the bottom of the page? More importantly, was your change recorded in the document?

so i wanted to see what are the field changes in GOA will not create a change version.
should i look only CDI ?

I don't think CDHDR or CDITM would determine if or not the fields would create version. Versioning is very SRM specific.

i could not see any any docuemnts. for eg. if i attach any change version must create right?

I would think so - when you just add a new attachment, a new version should be created. However, that said, I still think the table BBPD_COMP_FIELDS is the place to define the triggering of new version.

versions created. but logs are captured but i donot see attachemnts,

Come again? What logs did you mean? Did you mean that you added an attachment but after you saved it (release the contract), the attachment disappeared?