Currently it is not possible to create rules that include statement with two or more inverted selection criteria.

For example customer segment for everyone except account id a and b:
segment filter will translate this into accountid <> A OR accountid <> B => this filter rule is not filtering anything

Same for product hierarchy include hierarchy 1 and exclude a hierarchy on level 3

We would like to have multiple values per characteristic. For example; a certain product can be mounted using Glue, Screws and Rivets. In SAP ECC we are able to have multiple values, but Sana only displays 1 value.

See printscreen for more information.

We would like to have multiple values per characteristic. For example; a certain product can be mounted using Glue, Screws and Rivets. In SAP ECC we are able to have multiple values, but Sana only displays 1 value.

See printscreen for more information.

SANA only relies on sales hierarchy (MVKE). Not all organizations use that and only use the basic hierarchy (MARA). Maintaing the sales hierarchy is additional master data maintenance. Maybe an idea to have an option to also use the basic hierarchy.

To calculate balances / credit info, it seems SANA relies ONLY on credit control area as maintained in the customer master (KNVV). In standard SAP this field is not mandatory, if you don't maintain it SAP uses the credit control area as per the company code. When a company has no need to differentiate credit control area's under 1 company code for different sales organizations then maintaining on customer master is not needed. Maintaining that only for SANA need is additional master data maintenance.

To calculate balances / credit info, it seems SANA relies ONLY on credit control area as maintained in the customer master (KNVV). In standard SAP this field is not mandatory, if you don't maintain it SAP uses the credit control area as per the company code. When a company has no need to differentiate credit control area's under 1 company code for different sales organizations then maintaining on customer master is not needed. Maintaining that only for SANA need is additional master data maintenance.

Make it possible to make use of basic hierarchy (MARA) instead of only on sales hierarchy (MVKE). SOme organizations have no need to use the sales org2 view hierarchy, so it would be additional master data maintenance to enter that only for SANA use.