Configurations

Transaction Type (example: Quotation, sales order, service request, service contract, opportunity)

• It defines attributes and characteristics of business transactions
• In order to define transaction type, we need to first define control attributes (example: Org data profile, Partner determination procedure, status profile, text determination procedure, date profile)

Assign transactions as per below logic

Transaction type > Leading business transaction category > Assigned business transaction category > Item category > Item object type > Item category Goup

Item category is determined by

• Transaction Type
• Item category group (Product Master) (is distribution channel dependent)
• Item category usage
• Higher level item category

Text Determination: Structure of text determination

Create Text Object (Example: CRM_ORDERH)

Attach Text Determination Procedure (Example: ORDER001)

Attach Text Type (Example: 0001- Header Note)

Attach Access Sequence (Example: 01- Business partner text)

Attach Sequence (Example: 0001-Object business partner, Text type correspondence)

Attach Assignment Field (Example: Key field partner, Comm field sold to party)

Date Management (Date profile)

Path:

SPRO > CRM > Basic functions > Date management > Define date profile
SPRO > CRM . Basic functions > Date management > Define date types, duration types and date rule

It is a combination of date types (first note, header note, customer requirement note, internal note), duration and date rules (system calculates and enters the date automatically as programmed) to meet the requirement for the business in transaction documents.

To assign dates and durations to an item category, we have to group the date types and duration, together in a date profile and assign this date profile to transaction type or item type.

To avoid selecting it manually every time we create a document, we can calculate dates using predefined rules. So in date rules, we link date types, duration and any other rules with each other so we get calculation chains.

Status profile

Path:

SPRO > CRM > Transactions > Status Management > Change status profile for user status

In transaction documents, we do see various statuses (released, rejected, to release etc) which are controlled and configured by status profile.
If status profile (for user status) is not assigned to a transaction type/item categories, system status are displayed in the application (example: open, in processing, error, complete etc)

So in a status profile, we define user statuses, activation sequence of user statuses, initial/start status, transaction status (system status) that is connected with the user status.

Because these statuses appear somewhere in the transaction document, we must assign at least one object type (example: order header) to the status profile.

Incompleteness check

Path:

SPRO > CRM > Basic functions > Incompleteness

When we need to ensure that certain fields of information are mandatory in a transaction document (example: contact phone number or contact person), we can make settings for incompleteness check in the system in such a way that if there is no information entered in that field and user is trying to save the document, the system would give error message and provide one of the two options (warning or error message). 

First option is just show a warning that there is an incomplete field that user needs to take note of, but user can proceed further if they chose not to correct that error. Or, second option is that it will display the error message and won't let the user continue further unless that error has been corrected.

To set up incompleteness check, we can follow the below steps.

• Create incompleteness group for transactions
• Assign incompleteness group that you created to transaction type
• Create incompleteness procedure
• Create incompleteness procedure determination whereby you are attaching incompleteness group with the incompleteness procedure