There is a solution for the following problems:

It is about that the SolidEdge API does not manage to integrate Teamcenter items with mandatory attributes. The solution is to place the item in Teamcenter via the SOA_CLIENT before SolidEdge installs the part and then upload it to the prepared item. For this purpose, there are Configuration file ifseteamcenter.cfg following key to activate and 2 attribute sections for creating Items:

[CreationOptions]

#:HELP;If SolidEdge fails to create Teamcenter Items even when some/all of the workarounds 
 (<applyUploadFix>, <DocBeforeSave>, <DocOnSave>) are used, activate this to pre create 
 Teamcenter Items
#using Teamcenter public api (SOA_CLIENT). In this case the SolidEdge SaveAs API adds a 
 SolidEdge Dataset to the pre created Item when SaveAs is executed.
#Default is No.
#:VALS_M;"0","1";"No","Yes"
#:INACTIVE;PreCreateTeamcenterItems=0

#:HELP;Item (& ItemMaster) properties. Depending on your configuration it may be required to 
 also add these attributes to the section [Custom] using the
#SolidEdge attribute naming scheme <object>.<AttributeDisplayName> 
(e.g. Item.My custom attribute). Return-mapping is not supported in this section.
[Item_Attributes]

#:HELP;ItemRevision (& ItemRevisionMaster) properties. Depending on your configuration it may 
 be required to also add these attributes to the section [Custom] using the
#SolidEdge attribute naming scheme <object>.<AttributeDisplayName> 
 (e.g. itemRev.My custom attribute). Return-mapping is not supported in this section.
[ItemRevision_Attributes]